Why Mozilla Matters And Won't Switch To WebKit
Earlier this week, Opera announced that it would stop working on its own Presto layout engine and switch to WebKit. It's obvious that the open source WebKit engine currently has a lot of momentum behind it, with Google, Apple and now Opera backing it.
Context & Ripple Effects
Earlier coverage cast browser competition as a platform war, while a 2010 assessment argued Mozilla needed a survival strategy. Opera’s decision to end Presto development concentrates the immediate debate on whether browser makers should maintain their own rendering technology.
Mozilla’s refusal to join WebKit matters because Google, Apple and Opera are aligned behind the same open-source engine. The story is therefore about engine diversity and who retains leverage over web-platform implementation.
First-order effects
- Opera shifts development away from Presto and toward WebKit, while Mozilla keeps its own browser-engine path rather than adopting WebKit.
- Google and Apple gain another prominent WebKit backer, strengthening the engine’s developer and vendor momentum.
Second-order effects
- Web developers and browser vendors face greater incentive to prioritize WebKit behavior as Opera stops advancing Presto.
- Mozilla’s independent engine becomes a more consequential counterweight to implementation choices shaped by the Google, Apple and Opera WebKit coalition.
Third-order effects
- If engine consolidation continues, browser competition may move from rendering-engine design toward product features and distribution, with fewer independent implementations testing web standards.
- Mozilla’s choice points to a structural trade-off: adopting the dominant engine can reduce maintenance burden, but retaining an alternative preserves a check on platform influence.
The trend: Browser engines are consolidating around shared open-source foundations, making independent implementations more important to web-platform competition.