Google repeatedly pushes the web in a proprietary direction to improve its services on Chrome, making Microsoft's adoption of Chromium a loss for the open web
Peter Bright / Ars Technica :
Context & Ripple Effects
This piece lands days after Microsoft committed to rebuilding Edge on Chromium and investing in the engine — framed at the time as a bet on the web as an app platform (Edge's move onto Chromium). Peter Bright's argument inverts that framing: the consolidation hands Google, whose own apps and developer ecosystem already optimize for Chrome-first standards (Chrome-first optimization by developers), even more control over which web features become universal.
The concern is not hypothetical within this coverage — months later, reporting on Chromium's spread through new browser projects flagged Google's effective power over the web as a growing worry (Bloomberg's report on Chromium's spread).
First-order effects
- Microsoft exits the browser-engine business it once defined, leaving Google as the de facto maintainer of the engine that powers both Chrome and now Edge.
- Web developers lose one of the few remaining counterweights to Chrome-first feature shipping, reinforcing the divergence from the open web ethos already documented in early-2018 coverage.
Second-order effects
- New browser projects increasingly default to Chromium rather than building independent engines, compounding Google's gatekeeper position over web standards.
- Competing engine maintainers face shrinking relevance, raising the cost for any site or service that targets non-Chromium browsers.
Third-order effects
- If the pattern holds, web-platform governance effectively shifts to whatever Chrome ships first, converting an open-standards process into a single-vendor roadmap — the structural risk underlying later scrutiny of Google's power over the web.
The trend: Browser engines are consolidating around Chromium, shifting de facto control of web standards toward Google as independent engines retreat.