In a surprise announcement made at the Chromium Blog today, Google announced that Chrome OS, Chrome, and Opera will use a new rendering engine titled ‘Blink’. Blink is based of the current rendering engine WebKit. Google states the change is “not an easy decision,” but the change is necessary due to a ‘slow down of innovation.”
Google seems quite apologetic in the blog post, noting it understands the change may have significant implications for the web, but hopefully, in the long run, it will improve the health of the open web ecosystem.
It noted that the change will have little impact in the short-term to developers and Internet users, but Google hopes that the removal of the “multi-process architecture” will simplify the engine’s code and ease the difficulty required to develop for Chrome and Chrome OS. Ultimately, Google also hopes the new engine will speed up Internet load times.
The full press release via the Chromium Blog is available below.
WebKit is a lightweight yet powerful rendering engine that emerged out of KHTML in 2001. Its flexibility, performance and thoughtful design made it the obvious choice for Chromium’s rendering engine back when we started. Thanks to the hard work by all in the community, WebKit has thrived and kept pace with the web platform’s growing capabilities since then.
However, Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation – so today, we are introducing Blink, a new open source rendering engine based on WebKit.
This was not an easy decision. We know that the introduction of a new rendering engine can have significant implications for the web. Nevertheless, we believe that having multiple rendering engines—similar to having multiple browsers—will spur innovation and over time improve the health of the entire open web ecosystem.
In the short term, Blink will bring little change for web developers. The bulk of the initial work will focus on internal architectural improvements and a simplification of the codebase. For example, we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines—right off the bat. Over the long term a healthier codebase leads to more stability and fewer bugs.
Throughout this transition, we’ll collaborate closely with other browser vendors to move the web forward and preserve the compatibility that made it a successful ecosystem. In that spirit, we’ve setstrong guidelines for new features that emphasize standards, interoperability, conformance testing and transparency.
To learn more about Blink visit our project page.