Tom Warren:, writing for The Verge:
Something had to give. Microsoft had to change its Edge browser in a big way. That meeting with Nadella ultimately led to Microsoft’s huge decision to jettison the browser it built in house and start from scratch using Chromium as a new foundation. The stakes for success couldn’t be much higher: the future of Windows and the web itself could hinge on this project.
This is the story of how Microsoft made that monumental decision and what could happen next.
I’m not personally interested in Edge or particularly happy that Microsoft joined the Blink/Chromium camp. I would have definitely been more please had they based Edge on WebKit or Gecko…
And speaking of WebKit…
I’m deeply disappointed in Apple for discontinuing Safari for Windows and not expanding to Linux and other operating systems. I don’t trust Google or Microsoft’s priorities (Google’s especially), and Chrome needs to lose some market share for our benefit. History has shown that a monopoly in the browser department doesn’t end well. Apple had the unique ability to challenge Google on competing desktop OSes and they forfeited that fight. Yes, Safari is holding its own on mobile. For now. That could change, when something new comes along, replacing our iOS and Android devices. At this point, all I can do is also root for Mozilla and Firefox.
From the comments section:
From the description of the declarativeNetRequest API, I understand that its purpose is to merely enforce Adblock Plus (“ABP”)-compatible filtering capabilities. It shares the same basic filtering syntax: double-pipe to anchor to hostname, single pipe to anchor to start or end of URL, caret as a special placeholder, and so on. The described matching algorithm is exactly that of a ABP-like filtering engine.
If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (“uBO”) and uMatrix, can no longer exist.
Please don’t use Chrome (or Chromium unfortunately). Just switch to Safari or Firefox (I use it as my second browser and it’s fine).
And while you’re at it, switch out your search engine to DuckDuckGo — it works surprisingly well, even in Poland when searching for Polish content.
Microsoft’s Edge web browser has seen little success since its debut on Windows 10 back 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 launched with a plethora of issues which resulted in users rejecting it early on. Edge has since struggled to gain any 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, a rendering engine first popularized by Google’s Chrome browser. Codenamed Anaheim, this new web browser for Windows 10 will replace Edge as the default browser on the platform. It’s unknown at this time if Anaheim will use the Edge brand or a new brand, or if the user interface between Edge and Anaheim is different. One thing is for sure, however; EdgeHTML in Windows 10’s default browser is dead.
Having used many different browsers over the years, Safari has always appealed to me most for a number of different reasons. Since it was discontinued on Windows a few years ago, I have defaulted to Firefox on my only PC (I still naturally use Safari on my Mac), especially since Mozilla appears to be pushing privacy hard, but I really wish Safari was still around. I tried and tested Edge a few times, but it never appealed to me much. Chromium would be my second choice and I’m curious what Microsoft will do with it.