What makes you think they are not developing it themselves. They did buy Kiva for $775m.. It's a reasonable goal to automate the picker as the next step.
The purpose of such competition is to kindle interest, not to buy an already available solution. And to be reasonable, the winner is likely to be a partial solution at best.
That won't work very well. Many large h1b employers (say Microsoft) already have remote offices. If h1b becomes too expensive, they will just put people in other places that have loose immigration policies. AFAIK, Microsoft has the Vancouver office for a similar reason, to accomodate people if they can't to get h1b. Right now, these people will eventually move back to US on L1. But if neither H1b nor L1 is feasible, it's not entirely unimaginable that Microsoft will just expand the Vancouver office. Plus, Vancouver isn't really that far away from Redmond.
Hong kong stock exchange is okay with VIE. Tencent, for example, is listed in Hkex through VIE. The real problem is that Hkex is still reluctant to waive its 'one share one vote' rule. But, Alibaba's founder clearly wants to control the decision power. This kind of dual-class structure is common in US, but is forbidden in HK.
VIE is nothing new here. Granted, VIE is a risk, but it's a well-known and manageable risk.
I would assume this emulation layer is still not perfect. Say, many android apps have arm binaries. There are other subtle gaps in user differences as well. You really don't want to make it look like an android emulator for chrome os.
Exactly. These limitations are well known in the autonomous car community. These are not much harder to solve than what's been already solved. It makes sense to solve the majority of the cases and then start working on the edge cases.
My understanding is CAs have limited interest in this matter. The product they are selling to website owners is really that green lock in the address bar. As long as that green lock icon is there, SHA1 or SHA256 won't make any difference. In this sense, deprecation should actually start at the browser.
Slashdot Mirror
What makes you think they are not developing it themselves. They did buy Kiva for $775m.. It's a reasonable goal to automate the picker as the next step. The purpose of such competition is to kindle interest, not to buy an already available solution. And to be reasonable, the winner is likely to be a partial solution at best.
That won't work very well. Many large h1b employers (say Microsoft) already have remote offices. If h1b becomes too expensive, they will just put people in other places that have loose immigration policies. AFAIK, Microsoft has the Vancouver office for a similar reason, to accomodate people if they can't to get h1b. Right now, these people will eventually move back to US on L1. But if neither H1b nor L1 is feasible, it's not entirely unimaginable that Microsoft will just expand the Vancouver office. Plus, Vancouver isn't really that far away from Redmond.
You are assuming those 18000 folks laid off by MSFT are mainly US tech workers... which is very wrong...
Hong kong stock exchange is okay with VIE. Tencent, for example, is listed in Hkex through VIE. The real problem is that Hkex is still reluctant to waive its 'one share one vote' rule. But, Alibaba's founder clearly wants to control the decision power. This kind of dual-class structure is common in US, but is forbidden in HK.
VIE is nothing new here. Granted, VIE is a risk, but it's a well-known and manageable risk.
I would assume this emulation layer is still not perfect. Say, many android apps have arm binaries. There are other subtle gaps in user differences as well. You really don't want to make it look like an android emulator for chrome os.
Exactly. These limitations are well known in the autonomous car community. These are not much harder to solve than what's been already solved. It makes sense to solve the majority of the cases and then start working on the edge cases.
My understanding is CAs have limited interest in this matter. The product they are selling to website owners is really that green lock in the address bar. As long as that green lock icon is there, SHA1 or SHA256 won't make any difference. In this sense, deprecation should actually start at the browser.