I've been thinking a lot about Microsoft's transition to Chromium for Edge on desktops. There's the joke "Why do we need a chrome-driven edge? To download Chrome better? "But there is also the opposite:" Why should you even download Chrome if Edge is powered by Chromium? "
Yesterday's news made me think again about why I do not spend more time with Edge, especially considering Microsoft has done decent work with it. And the reality is that I can not give up on my Chrome extensions in particular.
Just as Firefox has developed against Internet Explorer and users have fallen in love with all third-party add-ons, I think that for many people, browser selection now amounts to supporting extensions. Almost all Web sites today work well in Edge, but if you rely on specific extensions, Edge is simply not an option.
(I'm not talking about users who do not really know what a browser is and that will be) Continue clicking on the "blue e" that brings them to "Google." This is probably the main reason why Microsoft made sure that the Edge logo resembles that of Internet Explorer, and probably that this new Chromium-powered Edge does not get rebranded.)
Microsoft expects it to be for developers It will be very easy to integrate your Chrome extensions into Edge. The details are still rare, but most Chrome extensions should work. If a handful of Chrome extensions I use are available on Edge, I certainly give Microsoft's browser a try.
The extension support is also the main reason why Firefox is installed, even though it is not my main browser. This makes me deadly, since Mozilla has responded to the announcement of Microsoft by Chromium.
Every now and then there is a big setback against Chrome, mainly because it's so dominant, and Google often does whatever it wants (Chrome) 63.60 percent market share for desktop browsers (according to Net Applications). The recent faux pas, however, were a particularly big headache, especially because Google still does not understand the problem it created.
Chrome 69 has attempted to "simplify" the handling of Google Site sign-in by also logging you in to Chrome when you log out, either from Chrome or from any Google site You signed out of both.
This led to a massive outcry by Chrome users, at least in part, because concerns were that the change meant the Chrome sync turned on. This was not the case (they still had to sync data like browsing history, passwords and Enable bookmarks to make them available on other devices). Still, for many it was still not good for Google to automatically sign them in Chrome just because they were signed in to a Google site.
Chrome 70 added an option to disable the linking of the web-based login to the browser-based login, tweak the interface a bit, and then re-enable auth cookies that you could do with this Stay logged in after the cookies were deleted. However, the main issue has not been addressed by Google: Chrome users should not have to disable auto sign-in when using Google Sites, but opt for if they want the functionality
Episodes like these and all the other things that Google does as a company whose parent earns almost all of its money with ads give reason to use other browsers. If Chrome extension support works, there will be frequent updates on my list next.
In announcing Chromium Edge, Microsoft promised to decouple Edge updates from Windows 1
So both things have to be done so I can give Edge a chance: Chrome extensions and frequent updates. However, once I've done that, Microsoft will need a reason to stay. Edge has interesting features to offer, including privacy enhancements, better integration with mobile devices, and of course performance improvements.
Google works in all these areas for Chrome to varying degrees. It will not be easy for Edge to break out.
But what does Microsoft have to lose with 4 percent market share?
ProBeat is a column in which Emil shakes over what crosses him this week.