The Browser Platform Wars
I was chatting recently with the founder of a high-profile startup that is making strategic use of Mozilla technology. “People keep telling me that WebKit is the future,” he complained. “Have we made the wrong choice?” — I did my best to reassure him of course …
Context & Ripple Effects
This 2009 snapshot catches the browser wars at an inflection point: engine choice had stopped being a technical detail and become a strategic bet, with startups building on Mozilla or WebKit codebases as the foundation of their products. The founder's anxiety — 'people keep telling me that WebKit is the future' — previews the consolidation to come: Chrome and its open-source Chromium sibling went on to power most new browser projects, raising concerns about Google's effective power over the web (Chromium's dominance in new browsers). It also foreshadows how engine monoculture would be weaponized: Apple later used its iOS WebKit monopoly to strip-mine and sabotage the web (Apple's WebKit gatekeeping), while Safari's glacial feature adoption showed what a single slow-moving steward costs everyone else (Safari's lagging web platform work).
First-order effects
- Startups choosing a browser engine in 2009 are making a multi-year architectural bet: the Mozilla-based founder here faces real switching costs and ecosystem pressure as talent and tooling drift toward WebKit.
- Mozilla's relevance as a platform substrate — distinct from Firefox's own fortunes — becomes a live question; its viability depends on third parties continuing to build on its technology.
Second-order effects
- Engine consolidation concentrates leverage: once Chromium became the default base for new projects, Google gained de facto veto power over web standards implementation, the dynamic Mozilla executives later described when Google properties broke outside Chrome (Google products breaking in Firefox).
- Competing engine stewards respond by differentiating on governance and openness — Mitchell Baker has framed Mozilla's history as battling Microsoft and working with rivals (Baker on Mozilla's history) — turning engine neutrality itself into a competitive pitch for platform builders.
Third-order effects
- If the pattern holds, browser engines collapse from many contenders into one or two de facto platforms, and the 'browser wars' shift from which engine wins to who governs the surviving engine — a structural dependency regulators and developers are still reckoning with.
- Platform builders learn that engine optionality is insurance: betting on a single steward exposes you to that steward's commercial interests, whether Apple's iOS restrictions or Google's search-business priorities.
The trend: Browser engines have consolidated from a contested field into near-monoculture, converting engine choice from a technical decision into a question of who holds gatekeeper power over the web platform.