Interviews with Microsoft executives shed light on the company's decision to rebuild its Edge browser with Google's Chromium, after Edge's flaws became clear
Tom Warren / The Verge :
Context & Ripple Effects
Microsoft's browser retreat has been unfolding in stages: the company announced in December that it would rebuild Edge on Google's open source Chromium and ship it to macOS, Windows 7, and Windows 8 — a reversal of its own-engine strategy — and by late March, hands-on coverage of the [[a:939892|first Chromium-powered Edge builds showed Chrome extensions working alongside a mixed Chrome/Edge UI]]. What was missing until now was the why. This piece closes that gap with executives acknowledging Edge's flaws directly, converting the move from a strategic pivot into an admission about the old engine.
First-order effects
- EdgeHTML is effectively dead as a product path: Microsoft's engineering effort now flows into Chromium-based Edge, and the browser's reach expands beyond Windows 10 to macOS, Windows 7, and Windows 8 users it previously couldn't touch.
Second-order effects
- Google's Chromium gains its most powerful corporate backer yet — Microsoft plans to invest in the engine rather than compete against it, shifting browser competition onto Chrome's home turf where Microsoft must differentiate on features like sync and UI rather than rendering.
Third-order effects
- If the pattern holds, web development consolidates further around a single dominant rendering engine, raising the stakes for whoever steers Chromium's roadmap and leaving engine diversity as a niche concern rather than an industry norm.
The trend: Browser markets are consolidating around shared open source engines, with even platform owners like Microsoft abandoning proprietary rendering to ride Chromium.