4 ms·

I'm wondering how, logistically, this make sense. Does Microsoft adopt Chromium/Blink for embedding in UWP apps and Electron? That will reduce memory and stora

I'm wondering how, logistically, this make sense. Does Microsoft adopt Chromium/Blink for embedding in UWP apps and Electron? That will reduce memory and storage requirements for the latter, but greatly increases the attack surface of the former. Microsoft is also taking on an _enormous_ maintenance burden in integrating it with their own sandboxing and protection mechanisms. I'm in disbelief that the ongoing cost of maintaining this fork and tying themselves to Chromium will be worth it. And the incentive for Google to now embed more and more ChromeOS/mobile device management into Chromium. For example: Google intends to ship an alternative credential provider for Windows 10 through Chrome. Microsoft will have to painstakingly isolate every feature like that which Google adds, and adopt an aggressive posture of doing code reviews of Chromium. I'm not sure how, given that they are such strong competitors/adversaries, this can work out.

stupidcar 8y ago
Nowadays most enterprise and bespoke intranet apps are targeting Chrome as a platform, not "the web". It's a re-run of the IE6 situation in the late 90s / early 2000s, except this time Microsoft is the victim, not the beneficiary. Whereas it used to be that big IT departments would nix the installation of any 3rd party browser, nowadays almost all accept the use of Chrome. And if you're selling an app into a big company, you always tell them to use Chrome, and never advertise IE/Edge support except as a last resort. If Microsoft want to sell their cloud services into these companies, they need to support Chrome-based apps. Edge won't do. As such, they have little choice but to fork it and build their own browser, tied into their services. I'm sure they recognise the potential problems and downsides, but consider it the least worst option at this point.
- iamstef 8y ago
  history doesn't repeat itself but it does rhyme...

stupidcar 8y ago

Nowadays most enterprise and bespoke intranet apps are targeting Chrome as a platform, not "the web". It's a re-run of the IE6 situation in the late 90s / early 2000s, except this time Microsoft is the victim, not the beneficiary. Whereas it used to be that big IT departments would nix the installation of any 3rd party browser, nowadays almost all accept the use of Chrome. And if you're selling an app into a big company, you always tell them to use Chrome, and never advertise IE/Edge support except as a last resort. If Microsoft want to sell their cloud services into these companies, they need to support Chrome-based apps. Edge won't do. As such, they have little choice but to fork it and build their own browser, tied into their services. I'm sure they recognise the potential problems and downsides, but consider it the least worst option at this point.

iamstef 8y ago
history doesn't repeat itself but it does rhyme...