The WebKit browser engine is becoming a less flexible foundation for open-source projects with the departure of Google from the project this week and Apple's consequent paring back of the project.
WebKit is a broad project that includes participation from many interested parties -- not just Apple and Google, but also BlackBerry, Samsung, Amazon, Oracle, Adobe Systems, and the programmers involved with the KDE and Gnome user interfaces for Linux. Indeed, the open-source project began as KDE's KHTML engine for the Konqueror browser before Apple got involved.
Google's departure means WebKit's sole remaining superpower, Apple, is streamlining the software. And that, in turn, means WebKit is becoming less a-la-carte, with a variety of modules and options and ways to extend it, and more prix-fixe, with a set collection of components.
That means that at least in some areas, it'll become harder to use WebKit as a foundation for other open-source projects that, like Chrome did, depart significantly from what Apple is doing with Safari.
But now? Tough beans.
"Supporting [Google's] V8 places a considerable burden on WebKit," said Apple's Oliver Hunt on the WebKit developer mailing list. "There are a number of large, cumbersome and expensive abstractions required to support multiple JS engines." If programmers don't like Apple's offerings, they should file bugs to request improvements, not add their own engines.
I personally would be reluctant to make that type of deal again.
Effectively, people looking for an open-source browser project now must choose between Blink and WebKit rather than being able to draw from a larger, broader code base. Of course, they also can choose Mozilla's Gecko, too, or its new.
At least in principle, WebKit and Blink each should now be a cleaner, more elegant engine, but no longer is there a broad project whose priorities are balanced by two major players.