WebKit 3's ten new tricks
As Apple's core rendering engine for Safari (and many third-party apps), WebKit has come quite a ways since its early days at Apple. Open sourced in 2005, its development has remained sure and steady, thanks to a reliable increase in Safari's adoption …
Context & Ripple Effects
Two years after Apple [[open-sourced WebKit in 2005]], the engine's development has settled into a steady public cadence rather than a closed, release-bound one — this roundup of ten WebKit 3 additions runs the same day the WebKit team itself catalogs them over on Surfin' Safari, which tells you how central the open tree has become to how Apple ships browser work.
The arc here started with tooling as much as features: the Web Inspector introduced in January 2006 signaled that Apple was investing in WebKit as a developer platform, not just a Safari component. With Safari adoption climbing — the stated reason development has stayed reliable — each engine drop now lands in both the browser and the growing set of third-party Mac applications that embed WebKit.
First-order effects
- Developers building on WebKit — whether in Safari or in the third-party Mac apps that embed the engine — get all ten capabilities in one drop, since the engine update carries the features everywhere WebKit goes.
- Apple converts Safari's rising market share into compounding engine investment: wider adoption means more testing surface and more external contributions landing in the open tree.
Second-order effects
- Because the tree is open, feature work no longer waits on Apple's own software schedule — external contributors can land improvements between Apple releases, raising the baseline every WebKit-embedding app inherits.
- Web authors gain a fast-moving reference implementation whose new capabilities raise expectations for what browsers should support, pressure that falls on rival engines to match feature-for-feature.
Third-order effects
- If the pattern holds, browser engines consolidate around open development models where vendor backing and community contribution coexist — the engine becomes shared infrastructure whose pace is set by the open tree, not by one company's product calendar.
The trend: Browser engines are shifting from single-vendor components to openly developed platforms whose feature velocity increasingly comes from the open source tree itself.