Google, the search engine giant is not only expanding, but also restructuring. Yes, there has been an official announcement that its flagship browser, Chrome will move to a new rendering engine, Blink. The decision has been taken by the company due to the fact that the new engine will be a fork of WebKit.

The incorporation are also introduced as the giant has plans of turning it into something that is better suited to be compatible for Chrome’s multi-process architecture. The main reason for Google introducing this change is the mere fact that the coding of WebKit has become more and more complex in recent times. All this is due to the extra popularity of WebKit. From one perspective it is good, but from a flip-side this leads to some issues as well.

From Google’s point of view the main problem is that its speed is restrained and this can hamper its expansion mode. The ideology back in 2010 for Google was to “Release early, iterate often” and that’s the mantra that still lingers . Thus, this calls for an entirely new browsing engine.

Estimations from Google’s end throws significant light on Blink’s codebase and the search engine giant points out that there can be immediate shedding of around 4.5 million lines of code stored in 7,000 files. This can be done by uprooting the unnecessary architectural bits from WebKit. The main reason for doing so is that this will not only make Blink lighter, but will also render it easy to be managed afterwards.

The actual key for success is being simple, together with speed. There is a tendency of Google to keep on posting releases, one after another. This spree is in six-weeks intervals and the trimmed version of the Blink code will suffice the tactics of Google, making life easier.

There has been a hand of both WebKit and Google in each other’s success. Google has contributed considerably over the past years, whereas the developers present at WebKit have also played a good part in the success story of Chrome. But, time’s changing and success for the search engine largely depends on the browser’s success as well. Thus, decisive action had to be taken by Google all the way, which makes it speed up the process or slow down.

Not solely depending on one browsing engine is a great ploy taken up by Google and it believes that the gamble will pay off. Blink is there to help it out to stay in the race and look for supremacy, as the Web rapidly expands. WebKit has other projects to cater to also and thus the synchronization of the engine with Google is mis-matched at this very moment. The search engine giant wants to move ahead at neck-break speed, whereas this might be fatal for WebKit, as it might not be able to keep up with the pace.

There’s tough competition in this category as well. Even if Blink manages to swipe away WebKit from the virtual space, Mozilla and Samsung will make sure that Servo makes life tough for Blink. Even Microsoft will be in the race to develop Trident for IE.

Thus a move-over to Blink can be a miss or a hit. Leave your comments and ideas in the comments section below.