First Blink-enabled Chrome stable build arriving in ten weeks: Google

Google has revealed that we might see the first Blink rendering engine powered Chrome stable build in around ten weeks. This comes just a day after Google announced its plans to switch from WebKit to Blink in its Chrome web browser. Blink is the new rendering engine by Google and is a forked version of WebKit designed to suit the need of Google.

 

Apparently, Chromium (the project behind Chrome) uses a different multi-process architecture unlike other WebKit based browsers and over the year of Chrome development, this has led to increased complexity. Google wants to remove this complexity and speed up development of Chrome and Chromium projects, thus the switch to Blink.

Chrome developers told the dev community in a Q&A panel that Blink is already integrated in the Canary builds of Chrome, and Google hopes to see the stable versions of its Chrome 28 with Blink for Android and the desktop within 10 weeks.

We can always see it Blink-powered Chrome earlier in the beta releases.  You can watch the entire Q&A panel for more information on Blink below.

Google to stop using WebKit rendering engine, introduces Blink

Google has announced that it is going to stop using the WebKit rendering engine in its Chrome web browser and will switch of Blink, which is a forked version of WebKit.  According to Google, this move will speed up development of Chrome as it will reduce complexity.

Google is not alone in this open-source Blink rendering engine move, Opera has also revealed that it will also be contributing to Blink in the future and it will be the new rendering engine to power Opera browsers. To remind you, Opera had very recently switched to WebKit for its Android browser.

Why the change to Blink?

Although, Google sings all praises for WebKit in its Blink announcement blog post, company notes that Chromium (the project behind Chrome) uses a different multi-process architecture unlike other WebKit based browsers and over the year of Chrome development, this has led to increased complexity. Google wants to remove this complexity and speed up development of Chrome and Chromium projects.

“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,” Adam Barth, Software Engineer, Google noted in a blog post.

What will be the implications for consumers or web developers?

In short term, very little for both, however in long term, consumers might notice some change on the front-end, developers will have to make the websites compliant with the Blink rendering engine and given the Chrome market-share and also Opera’s involvement, you can’t ignore it. Web developers can read more about Blink here.