The rise of Chrome and its open source Chromium sibling, often used in new browser projects, raises concerns about Google's effective power over the web
Gerrit De Vynck / Bloomberg : Tweets: @mdudas , @samharrelson , @gerritd , @gerritd , @hannah_recht , and @gerritd Tweets: Mike Dudas / @mdudas : Incredible execution by Google to make @googlechrome the clear web browsing leader. It's by far the best product on the market https://www.bloomberg.com/... https://twitter.com/... Sam Harrelson / @samharrelson : I've been using Chrome since the betas a decade ago. It definitely dominates my usage of the web. My iconoclastic self gets troubled by that often, but there's a feeling of “what then... Firefox?” https://twitter.com/... Gerrit De Vynck / @gerritd : Chrome's source code is open for anyone to borrow, and now most smaller browsers use it. That means browsers like Opera, Brave and even Microsoft Edge rely on Google engineers to maintain their code Gerrit De Vynck / @gerritd : Google insists it only wins when the web stays free and open, and that they aren't out to quash competitors with Chrome's dominance. That's not how everyone feels though... Hannah Recht / @hannah_recht : hello it is me, your neighborhood Firefox developer creeping in your DMs to tell you that your bespoke web page is broken in Firefox https://www.bloomberg.com/... pic.twitter.com/HDmiFQCpIC Gerrit De Vynck / @gerritd : In 10 years Google's Chrome has gone from a nothing to the browser of choice on more than 2 out of 3 computers globally. That's given Google unprecedented control over the future of the web https://www.bloomberg.com/...
Context & Ripple Effects
Bloomberg's piece lands at the moment Chrome has become the browser of choice on more than two-thirds of computers globally, with Opera, Brave, and Microsoft Edge all building on the Chromium codebase that Google engineers maintain. That means even nominally rival browsers ship Google's engine, so the earlier reporting on developers optimizing for standards that first ship in Chrome reads less like a drift and more like a structural outcome.
The compatibility pressure is already visible: Firefox developers report bespoke pages breaking in their browser, echoing the trust erosion from Chrome 69's silent forced-login change. With Mozilla under financial strain per later coverage, the question is whether any non-Chromium engine can stay viable enough to keep the web multi-engine.
First-order effects
- Firefox faces a compounding burden: beyond losing share to Chrome, its developers must chase bespoke pages built against Chrome-first behavior, making every incompatibility look like Firefox's fault rather than a standards divergence.
- Opera, Brave, and Microsoft Edge are effectively dependent on Google's engineering cadence — their differentiation is limited to features layered on top of an engine whose roadmap Google controls.
Second-order effects
- Google's own apps and services can adopt new web capabilities before they are standardized, forcing competitors' browsers to implement Google-defined behavior or break on the most-used sites — pricing power over 'web compatibility' effectively accrues to Google without a transaction.
- Publishers and software distributors become sensitive to unilateral Chrome policy shifts, as seen when Chrome's malware flagging stifled indie software distribution — one company's client-side rules now function as de facto web-wide policy.
Third-order effects
- If the pattern holds, the browser layer consolidates into a single de facto implementation with nominal forks, mirroring the walled-garden trajectory later coverage describes for Chrome, Android, and AdWords together — and inviting the same regulatory scrutiny applied to Apple's iOS WebKit control, which critics argue drains the web of future potential.
- A single-engine web removes the market feedback loop that once forced browsers to compete on standards fidelity, shifting enforcement of openness from competition to regulators and standards bodies with no commercial lever.
The trend: Web browsing is consolidating around one company's engine and its open-source sibling, converting browser choice into a gatekeeper-leverage question rather than a product-choice one.