TECH
Microsoft is scrapping Edge, switching to just another Chrome clone
Windows Central reports that Microsoft is planning to replace its Edge browser, which uses Microsoft's own EdgeHTML rendering engine and Chakra JavaScript engine, with a new browser built on Chromium, the open source counterpart to Google's Chrome. The new browser has the Anaheim codename.
The report is short on details. The easiest thing for Microsoft to do is to use Chromium's code wholesale-the Blink rendering engine, the V8 JavaScript engine, and the Chrome user interface with the Google Account parts omitted-to produce something that looks, works, and feels almost identical to Chrome. Alternatively, Redmond could use Blink and V8 but wrap them in Edge's user interface (or some derivative thereof), to retain its own appearance. It might even be possible to do something weird, such as Blink with the Chakra JavaScript engine. We'll have to wait and see.
Since its launch with Windows 10, Edge has failed to gain much market share. The first iterations of Edge were extremely barebones, offering little more than a basic tabbed browser-no extensions, little control over behavior. Early releases of Edge were also not stable as one might have liked, making the browser hard to recommend. Three years later on and Edge is greatly-but unevenly-improved. The browser engine's stability seems to be much better than it was, and performance and compatibility remain solid (though with the exception of a few corner cases, these were never a real concern).
What has consistently let Edge down is the stuff around the engine. Tab handling remains rudimentary, for example; it's still all too easy to make Edge lose my meticulously pinned, organized tabs, presenting me with an empty browser window. Cross-device syncing falls short of that provided by Chrome. Chrome's integrated password manager is vastly superior to Edge's. The number of extensions available is limited (though this is a little double-edged; Microsoft's carefully vetted set of extensions sidesteps the significant issues that Google has had with malicious Chrome extensions).
Swapping out the engine does exactly nothing to remedy these problems. It's not EdgeHTML and Chakra that are preventing Microsoft from providing the really first-rate browser interface; it's the fact that Microsoft has not prioritized this work. There's nothing magical about Blink or V8 that makes the Chrome password manager better than Edge's; Google has taken the time to do the work.
If Microsoft does this work for Anaheim, one wonders why it did not bother doing it for Edge. Conversely, if Microsoft does not bother doing this work for Anaheim either, then who even cares? Users would be better served by sticking to Chrome anyway. Abandonment issues
Abandonment of Edge may also have consequences for the development of Web standards. The process currently used by the World Wide Web Consortium (W3C; the industry body that oversees development of HTML, CSS, and some related standards) requires the demonstration of interoperable independent implementations of any new feature before that feature can be standardized. This ensures that the features are not too tied to the specific implementation of any one browser. With Apple often indifferent to features that Microsoft and Google have prioritized, this leaves only Mozilla as a consistent supplier of independent implementations, further increasing the burden on the open source organization.
A switch to Blink also raises the specter of a return to Internet Explorer 6's heyday, when Web pages were designed not for Web standards, but specifically for the quirks and oddities of Microsoft's then-dominant browser. The desktop will be owned by Blink, with the mobile space split between Apple's WebKit and Android's Blink.
Microsoft is expected to make an official announcement some time this week. Peter Bright-Peter is Technology Editor at Ars. He covers Microsoft, programming and software development, Web technology and browsers, and security. He is based in Brooklyn, NY.
No comments:
Post a Comment