The Dawn of the Modern Browser Engine
To understand WebKit's impact, you have to go back to the late 1990s. The browser wars were raging, and the engine that renders a webpage—the complex software that turns HTML and CSS into the vibrant sites we use daily—was a key battleground. At the time,
a small, clean, and standards-compliant engine called KHTML was being developed for the Linux desktop environment. It was good, but it was a niche player in a world dominated by Microsoft's Internet Explorer.
Apple's Fork and a Pivotal Decision
In the early 2000s, Apple needed a modern browser engine for its new Safari browser. Instead of building from scratch, it chose to “fork,” or create its own version of, KHTML and its JavaScript counterpart, KJS. Apple dubbed its new creations WebCore and JavaScriptCore, which together formed the heart of a new open-source project: WebKit. But the most important choice wasn't technical. KHTML was licensed under the GNU Lesser General Public License (LGPL). Apple decided to keep this license for its new project. This decision, seemingly a bit of legal housekeeping, would go on to define the next decade of the web.
Why the LGPL Was a Game-Changer
Open-source licenses aren't all the same. A strict "copyleft" license like the standard GPL requires that any software that incorporates GPL code must also be made open source. This is great for fostering a purely open ecosystem but can be a dealbreaker for commercial companies that want to protect their proprietary code. The LGPL, however, is different. It allows developers to use an LGPL-licensed component (like a rendering engine) in their own proprietary, closed-source application without having to release their own code. They only need to share any direct modifications made to the LGPL component itself. For Apple, this meant it could build its Safari browser, keeping its unique features private, while still using and contributing to the open-source WebKit engine at its core.
Enter Google: The Unlikely Beneficiary
This licensing choice created the perfect opportunity for Apple's biggest rival. When Google decided to build its own browser, Chrome, it needed a world-class engine. Mozilla's Gecko engine was deeply tied to Firefox, making it hard to adapt. But WebKit, thanks to its LGPL license, was the perfect candidate. It was fast, standards-compliant, and, most importantly, Google could use it as the foundation for Chrome without being forced to open-source all of Chrome's surrounding code. Google became a major contributor to the WebKit project, pouring resources into improving the engine that both Chrome and Safari relied on. This arrangement allowed for years of shared progress, rapidly advancing web technology for everyone.
A Legacy Written in Law, Not Just Code
The story took another turn in 2013 when Google forked WebKit to create its own engine, Blink. The goal was to have more freedom and to trim down the code to suit Chrome's specific needs. Today, Blink powers not only Chrome but also Microsoft Edge, Opera, and many other browsers. Safari continues to use WebKit. The result is a web dominated by two engine families that share a common ancestor. This divergence happened, just as WebKit's creation did, because the license permitted it. The decision by Apple to stick with the flexible LGPL created a competitive and collaborative dynamic that fueled browser innovation. It allowed other corporate giants to build upon its work, leading directly to the browser landscape we have today. Without that license, Google Chrome might never have existed in the form it does, and the web would look very different.
