I'd really like to understand the rationale behind this choice. What they'd like to leverage from Chromium that Blink alone wouldn't have?
Microsoft Edge and open source collaboration
11–20 of 304 posts
Re: Microsoft Edge and open source collaboration
#12This is HUGE! Microsoft throwing away the IE engine in favor of one more or less standard rendering engine is a huge win for web developers everywhere! It's also something that would have been unimaginable in the Steve Ballmer era. Thank you!
Re: Microsoft Edge and open source collaboration
#13Edit: We all know why they want everyone to switch don't we, but think about all the now admittedly false marketing! It's not like they stopped the aggressive marketing for a few years and now saying that they can no longer keep up. They probably are doing it now still and implying that Edge is better. Is the marketing really so uninformed about such big decisions?
Re: Microsoft Edge and open source collaboration
#14This is HUGE! Microsoft throwing away the IE engine in favor of one more or less standard rendering engine is a huge win for web developers everywhere! It's also something that would have been unimaginable in the Steve Ballmer era. Thank you!
And a huge loss for users everywhere. Now that Chrome is becoming the main web target, Google (an adtech company) basically controls the internet.
Re: Microsoft Edge and open source collaboration
#15This is HUGE! Microsoft throwing away the IE engine in favor of one more or less standard rendering engine is a huge win for web developers everywhere! It's also something that would have been unimaginable in the Steve Ballmer era. Thank you!
Re: Microsoft Edge and open source collaboration
#16Re: Microsoft Edge and open source collaboration
#17EdgeHTML is also used for embedding HTML into UWP, and controls have been released for WPF and Win32. I wonder what will be the story of that. Will that be transparently changed to Chrome, can it be changed to Chrome or will EdgeHTML be used only for that?
Re: Microsoft Edge and open source collaboration
#18In short. Edge engine is dead. Based on Chromium. Not an UWP. Will be on Windows 7 and Mac.
Microsoft, in its short-sighted way, thought that tying the browser to Windows would be an "advantage," because of things like "better integration with the OS" and throwing the Edge updates in there with the Windows updates, without needing a different update channel.
However, this was short-sighted was because of the following reasons:
- Edge development would remain very sluggish compared to the development of Chrome and Firefox, as new major features would have to wait until Windows itself gets new major features (which happens every 6 months, rather than 6 weeks).
- It would mean Edge would not be cross-platform, a huge strategic mistake on Microsoft's part. People want to use the same browser across devices.
- The proprietary "features" Microsoft would build in Edge over time that only work with certain versions of Windows will come back to bite it in the ass in the future.
Re: Microsoft Edge and open source collaboration
#19In short. Edge engine is dead. Based on Chromium. Not an UWP. Will be on Windows 7 and Mac.
Re: Microsoft Edge and open source collaboration
#20This is HUGE! Microsoft throwing away the IE engine in favor of one more or less standard rendering engine is a huge win for web developers everywhere! It's also something that would have been unimaginable in the Steve Ballmer era. Thank you!
Competition is good. Monoculture is bad.
That said, supporting all of the standards in a way that makes everyone happy is completely impossible. And if you're not in first place, it's just Cost, Cost, Cost for you.
I don't blame them for doing this, but I'm sad about it.