Google's announcement that it would
fork WebKit to develop its own Blink browser engine was definitely a surprise and the repercussions of this move for the browser ecosystem as a whole are stil
Ardian Ludwig, Google's lead engineer for Android security, on Friday revealed the decision was due to the complexity of applying patches to older branches of WebKit - the browser engine that was used in WebView and Chrome until Google
forked WebKit into Blink for Chrome.
Not exact matches
Google had worked on its stock Android browser as a separate
fork of
WebKit, but with the arrival of Chrome for Android, the mobile version of its browser is being integrated with the ordinary
WebKit project.
As noted, Android was part of the
WebKit world until the very recent
fork to Blink.
The four big browser families, according to Wikipedia, are «
WebKit» (Wikipedia), used in Safari; «Blink (layout engine)» (Wikipedia), a 2013
fork of
WebKit used in the newest versions of Chrome and Opera; «Gecko (layout engine)» (Wikipedia), used in Firefox; and «Trident (layout engine)» (Wikipedia), used in Internet Explorer.
Chrome is using a special version (known as a
fork) of the
WebKit engine developed by KDE in 1998 known as Blink.
Here, Opera, which is based on Google's open - source Chromium web browser, and Blink, Google's
WebKit web browser engine
fork, took first with 757.5 milliseconds (ms).
Forking their own model will alleviate future issues in both the
WebKit code and Chrome itself.
Director of engineering for the Web Platform team at Adobe Vincent Hardy has announced that Adobe will contribute to Google's new Blink browser engine A week or so ago, we talked about Google
forking off
WebKit to create their own browser rendering engine.