Google Kills Webkit, Moves To New Blink Rendering Engine For Chrome

chromiumIn what can only be described as a “buzz kill”, Google will stop using the WebKit engine inside of Chrome, instead opting for one it’s creating: called “Blink.” What this means is that the engine used to actually display web pages inside of the browser will be changed, but according to Google, it’s for the better. Apparently, Google says that it is to speed up development on Chrome, thanks to reducing complexity of actually coding for the browser.

Chrome uses some slightly different processes for making web pages load (a “multi-process architecture,” which helps keep your other tabs running when a web page crashes, you can probably see this happening in your task manager), but when trying to mesh its innovative technical setup with the rest of WebKit — also used on Apple’s Safari — it made Chrome more prone to bugs, crashes, and everything icky about bad coding when making computer apps.

In the long run, it’s may mean that website developers (and some app devs) will need to make some changes to their existing work to support the Blink engine, but for the short-term, it seems like things won’t be of much issue. I think it’s a great move, further moving away from the most-used web rendering engine and creating something that works better for everyone that uses Chrome. How Google goes about doing that, the right way, remains to be seen, like issuing an update to Chrome to start this change.

Via: Chromium Blog, Blink