You probably heard the news already but if not here it is
Microsoft is building a Chromium-powered web browser that will replace Edge on Windows 10
Microsoft is throwing in the towel with Edge and is building a new web browser for Windows 10, this time powered by Chromium.
Microsoft's Edge web browser has seen little success since its debut on Windows 10 in 2015. Built from the ground up with a new rendering engine known as EdgeHTML, Microsoft Edge was designed to be fast, lightweight, and secure, but it launched with a plethora of issues that resulted in users rejecting it early on. Edge has since struggled to gain traction, thanks to its continued instability and lack of mindshare, from users and web developers.
Because of this, I'm told that Microsoft is throwing in the towel with EdgeHTML and is instead building a new web browser powered by Chromium, which uses a similar rendering engine first popularized by Google's Chrome browser known as Blink. Codenamed "Anaheim," this new browser for Windows 10 will replace Edge as the default browser on the platform, according to my sources, who wish to remain anonymous. It's unknown at this time if Anaheim will use the Edge brand or a new brand, or if the user interface (UI) between Edge and Anaheim is different. One thing is for sure, however; EdgeHTML in Windows 10's default browser is dead.
here the first reaction on hacker news
so yeah Microsoft plan to replace EdgeHTML with Chrome and yeah that's making everyone talk and for good reasons
then another post followed
The State of Web Browsers
Late 2018 edition
Yesterday, Windows Central published a rumour that Microsoft is ditching its Edge browser, or more accurately put, to relaunch a new browser using the Chromium engine. The rumour has been picked up by mainstream media and as far as I know, not denied by Microsoft, therefore I assume it to be factual. A good reason as any for me to share some thoughts on the current landscape of web browsers.
If you’re new to my blog, I’ll add the background that I’ve been in the web game since 1996, and have seen every iteration of the browser wars up close. In terms of mindset, I’m from the Zeldman school of thought: a deep believer and proponent of the open web, web standards, a shared web.
I’ll also warn you that I am direct, frank, cynical, love dark humour, and don’t take many things serious, including myself. With that in mind, let’s go.
and in the hacker news comments
you can read this interesting tidbit
As a Mozilla employee, speaking from my own limited perspective, it seems the company as a whole broadly agrees with this analysis even if it isn't vocalized quite this succinctly. Chrome started out being force-installed alongside Flash, and there is no solution to the bundling problem -- the problem is even larger in scale than the article suggests because of Chromebooks affecting desktop. People who use Firefox in the future will increasingly be people who do so consciously, presumably because they view Mozilla as helping them protect their privacy. Chrome is and will continue to be the default.
Eventually, Google will do something that is an abuse of their monopoly power. Either there will eventually be a privacy/creepiness fiasco, or Google will attempt to use Chrome as leverage to squeeze a competitor out of a market.
When that happens, Mozilla will be well-positioned as an alternative. The path forward in this view would look more like Mozilla as a constellation of disaffected companies and users attempting to free themselves from Google. It won't look like Mozilla on the side doing something by itself. We will largely be defined in opposition to Google.
The article correctly points out that a wiser Microsoft could have gotten a head-start on this inevitability by partnering with us early.
and among many others articles and posts here a selection
Microsoft Edge goes Chromium (and macOS)
The rumors were true: Microsoft Edge is moving to the open-source Chromium platform, the same platform that powers Google’s Chrome browser. And once that is done, Microsoft is bringing Edge to macOS, too. In addition, Microsoft is decoupling Edge from the Windows update process to offer a faster update cadence — and with that, it’ll bring the new Edge to Windows 7 and 8 users, too.
and from on MSFT
More Edge/Chromium info comes to light – will support Chrome extensions, more on PWAs
We’re still digesting the implications of Microsoft’s momentous decision to move Edge from its proprietary browser engine, EdgeHTML, to the open source Chromium. While this is indeed a huge change, the devil is in the details, especially with EdgeHTML being so intertwined with both Windows 10 itself as well as with Microsoft’s sputtering efforts at embracing Progressive Web Apps (PWAs) and the Universal Windows Platform for apps (UWP). Much has been written about what’s happening with Edge, including Joe Belfiore’s announcement post, a statement of “intent” by the Edge team on GitHub, and in numerous posts and Tweets scattered across the web.
Yesterday, in a post on Reddit linking to the Belfiore announcement, one redditor wasn’t overly impressed, which prompted a response from Kyle Alden, Microsoft’s Edge Project Manager. Here’s what he said:
Some responses to your questions –
- Existing UWP apps (including PWAs in the Store) will continue to use EdgeHTML/Chakra without interruption. We don’t plan to shim under those with a different engine. We do expect to offer a new WebView that apps can choose to use based on the new rendering engine.
- We expect to provide support for PWAs to be installed directly from the browser (much like with Chrome) in addition to the current Store approach. We’re not ready to go into all the details yet but PWAs behaving like native apps is still an important principle for us so we’ll be looking into the right system integrations to get that right.
- It’s our intention to support existing Chrome extensions.
and here the official announcement by Microsoft
Microsoft Edge: Making the web better through more open source collaboration
For the past few years, Microsoft has meaningfully increased participation in the open source software (OSS) community, becoming one of the world’s largest supporters of OSS projects. Today we’re announcing that we intend to adopt the Chromium open source project in the development of Microsoft Edge on the desktop to create better web compatibility for our customers and less fragmentation of the web for all web developers.
As part of this, we intend to become a significant contributor to the Chromium project, in a way that can make not just Microsoft Edge — but other browsers as well — better on both PCs and other devices.
So yeah... almost everyone is using chrome, except firefox
I searched among the many things that have been said and I did not find a clear reference about the JS engine, a lot of people assume that, by adopting chrome, Microsoft will also adopt the V8 engine, but personally I'm not so sure.
Look at TypeScript, when distributed with VS Code, TS is running with Chakra (the MS JS Engine), and on other old news when MS open sourced ChakraCore they also made it work with Node.js (replacing the original v8 JS engine from Google).
Another thing is that when MS will reuse Chrome for the rendering of HTML and publish their own browser (still named Edge) it will make less an incentive for people to go and download Chrome, and they do plan to publish that Edge browser based on Chrome to macOS.
Anyway, developers are already testing only for Chrome so less hassle I suppose.
No, the real problem is too much power into one place, that make Google almost solely in control of the web platform, as rightly mentioned here
so yeah not Firefox, well... not yet, but does it really matters when their browser is around 10% ?
and here the official comment of Mozilla
Microsoft is officially giving up on an independent shared platform for the internet. By adopting Chromium, Microsoft hands over control of even more of online life to Google.
if Google decide that autoplay HTML5 in your face is a good thing (business wise) for their advertising platform, there is not much you can do ... that's the problem imho
Let's see how all that pan out in the long run