14 DAY TRIAL // One thing that Google didn't make immediately clear when it announced Blink, the new browser engine to be used in Chrome, was when Blink would end up in the browser. After all, it's a major project and Google has big plans for it.
But since Blink, at this stage, is still very much identical to WebKit, it will end up in Chrome 28, currently being prepared for the dev channel. There are Chromium 28 builds and Chrome Canary 28 builds, though they both still use WebKit.
That will change over the coming days, though, again, as far as users and even web developers are concerned, there will be no difference between Chrome with WebKit and Chrome with Blink.
That's not to say they will be identical, Google's first order of business is to remove code it doesn't need anymore, like code specific to platforms Chrome is not available on, Symbian or iOS, or code for WebKit2.
But most of that code didn't end up in the compiled WebKit for Chrome anyway. There will be some differences between the compiled WebKit and Blink, but they will be minor.
Google does have some bigger changes planned though, once it's done removing code it definitely doesn't use, it will start removing or changing code that was there only to support other browsers that rely on WebKit.
Later on, Google will start rewriting some bigger portions of the code, in ways that make more sense for Chrome and with speed in mind.
One of the first big changes will be out-of-process iframes, running iframe code in a separate process, isolating it from the process of the page containing the iframe. This has plenty of benefits from a security point of view.
Google also plans to rewrite the networking code to make it simpler and faster. It couldn't do that until now with WebKit because the code had to respect some old Mac WebKit APIs.