Google and Opera had announced that they will be moving their browsers away from the open source WebKit rendering standard to the new forked, Google-developed Blink standard in the future. The move would affect Google Chrome browser, Chrome OS, and the Opera browser.
“This was not an easy decision,” Google writes in its blog. “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.”
According to the Chrome-maker, the move away from WebKit is because 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.” As such, Google is developing its own Blink standard, which will also be an open source rendering engine that’s based on WebKit.
However, unlike WebKit, Google will be selective about the developers it chooses to work with.
It’s unclear if the move away from WebKit has a political nature. WebKit’s origins came from within Apple before the firm decided to open source the development engine. Since then, it’s been powering some of the most popular browsers on the Internet, including Safari, mobile Safari on iOS, the Android browser, the BlackBerry 10 browser, and others. With Google standardizing on the mobile Chrome browser on the most recent builds of Android, rather than relying on the Android browser, Blink will make its way into Android as well.
For Internet surfers and web developers, the move to Blink will have little change or noticeable impact. Most of the changes will be under the hood and Blink will try to streamline the architecture. By removing unnecessary codes, Google says that this will lead to improved stability for browsers.
Competing Internet Explorer by Microsoft relies on the Trident engine while Mozilla’s Firefox browser uses Gecko, rather than Webkit. Opera, which had recently switched from its Presto rendering engine to Webkit, had recently confirmed to The Next Web that it would follow Google’s lead to adopt the forked WebKit version known as Blink.
How to Take an ECG on the Apple Watch
This guide will show you how to take an ECG with the Apple Watch 4. This is a new feature...
3 Reasons Not to Install watchOS 5.1.2 & 9 Reasons You Should
The watchOS 5.1.2 update brings a massive new feature to the Apple Watch with ECG support and a collection of...