It won't be long before Google bids adieu to WebKit for its Chrome browser. The technology giant recently announced its browser will switch to the Blink rendering engine, which is an open source rendering engine based on WebKit. Google stated the reason behind the switch is because Chromium uses a different multi-process approach than other WebKit browsers, which has led to increased complexity. It's also been slowing down innovation, so in a way to curb all of that, there's Blink. Google didn't come to that conclusion lightly however, as a new rendering engine can introduce significant changes to the Web as a whole. What the company is banking on is having more rendering engines will lead to more innovation and improves the Internet's ecosystem.
Blink allows Google to strip out a ton of unnecessary components on Chrome, with initial figures of 4.5 million lines of code being removed. That equates to seven build systems and 7,000 files with the first switch, which can only mean good things for the browser. Long term it should lead to more stability and less bugs, so that's a welcomed benefit. Google's Chrome OS is going to switch over to Blink, as will the Opera web browser, which moved to WebKit barely two months ago.
Google is set to implement Blink in build 28 of Chrome that's due in about ten weeks, but it's already available in the Canary version for developers and early adopters. More information on Blink can be found here.