Friday, April 5, 2013

Google's switch to Blink arrives in ten weeks with Chrome 28

Google's switch to Blink arrives in ten weeks with Chrome 28

Google's switch to Blink arrives in ten weeks with Chrome 28

Google just launched the Chrome 27 beta, and already it's talking about Chrome 28 - which will include the recently announced switch to Blink.

Blink is the new rendering engine that will replace WebKit across all of Google's operating systems and browsers.

Blink will arrive alongside Chrome 28 in about ten weeks' time, Google revealed in a Q&A video, posted yesterday, that explains the company's decision to fork WebKit.

The video is embedded below, so check it out if you're curious what Google is thinking.

YouTube : youtubeurl

Change is in the air

On Thursday, Google announced plans to fork the widely-adopted rendering engine WebKit and develop its own rendering engine, based on WebKit, called Blink.

Google software engineer Adam Barth wrote Thursday that Google believes 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."

WebKit currently powers both Apple's Safari browser and Google Chrome, accounting in total for 40 percent of browser usage.

That's about to change, obviously, and it's unclear what implications Google's Blink switch will have for the future of the web.

Spring cleaning

Barth did reveal Google's initial reasoning: "In the short t erm, Blink will bring little change for web developers," he wrote. "The bulk of the initial work will focus on internal architectural improvements and a simplification of the codebase."

"For example, we anticipate that we'll be able to remove 7 build systems and delete more than 7,000 files - comprising more than 4.5 million lines - right off the bat."

Blink is supposed to replace WebKit in Chrome on all platforms, though Apple's iOS - a platform on which browsers are required by Apple to use WebKit - is conspicuously not mentioned in the above video.


No comments:

Post a Comment

//PART 2