Microsoft Edge on Windows 10 may be dropped for a new blink-based browser
edl last edited by edl
Thought this was interesting and wise of Microsoft...
I find this to be both cause for celebration and concern.
The windows browsers have largely been... not great in terms of keeping up with web standards. Edge and EdgeHTML were a damn sight better than IE and Trident ever were, but they still lagged behind. Microsoft adopting another engine will be good for their users.
However, this is just going to further fuel the homogeneous browser environment. Basically the only non-chrome browser going forward will be browsers based on Mozilla's rendering engine. This is not a great position to be in.
(At least they're not building a browser on top of electron.)
Depending on how web developers handle this it could result in either a decrease in the number of sites "built for chrome", or even an increase if things go awry.
One good thing though: the Microsoft store policy of not allowing browsers that don't use the EdgeHTML rendering engine is no longer a viable policy. This could allow it to open up to others, such as Vivaldi.
I did read in one of these articles that Microsoft engineers were contributing code to get chromium working on ARM (for their Windows on ARM surface products). Hadn't Vivaldi already got this working?
LonM last edited by Pesala
Mod Edit: Threads merged.
It seems this whole story rose from this one windowscentral article, and the only source they give is "I'm told that..." and something anecdotal about devs wanting to get chrome working on windows for ARM.
Until we get an official notice from Microsoft, these are rumors and naught more.
The rumours have been confirmed, as per https://github.com/MicrosoftEdge/MSEdge
Steffie last edited by
It's sad news. Now i'll have to revert to mocking only Chrome, whereas before i could evenly distribute my mocking across two useless pixel aggregators.
I had some thoughts on this, I'll repeat what I said on twitter.
The move of @MicrosoftEdge to chromium will be a blow to standards. Yes, everyone should keep on spec, but having more engines allows them to experiment with different technologies before standardisation is complete.
In their own announcement they state that: "he open web benefits from open debate from a wide variety of perspectives" - how can this take place if 90+% of developers only care about a single engine? The only real debate to be had is from Mozilla.
It would be a good idea for @MicrosoftEdge to open source whatever remains of Edge regardless. Chakra already is, and if they're not developing it any more MS stand nothing to lose by sharing it. This also benefits anyone who does want to take it forward.
I am also dismayed at @MicrosoftEdge's notice that it's too difficult for developers to test multiple engines. Encouraging developers to build for few (read one) engine is what led to the IE compatibility disaster decades ago.
If MS wanted a more open approach they simply could have made the entire browser open source from the beginning. Abandoning it now does very little good for browser standards and developers other than saving MS some money.
I'm perhaps taking a bit of a negative stance on the @MicrosoftEdge issue. If this leads to better performance and more distributed browser there, then that's definitely a benefit. But this was definitely one of the stranger ways MS could have taken.
ROTFL last edited by