Chrome browser: Blink is accelerating the replacement of WebKit

In February this year, Google announced that it "will take 10 weeks to replace the existing Chrome browser engine WebKit on all its platforms with the new rendering engine blink." At a recent GOOGLEI/O developer meeting, the Blink team said they had removed 8.8 million lines of code from the original WebKit.

Blink engine

Google introduced a few months ago, the blink engine at this stage to streamline the internal structure of the main, in the near future will delete about 7,000 files and 4.5 million lines of WebKit2 compatible code. And as it is today, Google's efficiency in removing webkit is far more than expected.

In addition to removing code, the Blink project team now includes new experiments, such as the Lazyblock layout, to check whether the engine can speed up the size of the large webapp by processing the on-screen display first. The result of the current experiment is that the rendering time is reduced from 4 seconds to 32 milliseconds.

About Blink engine

Blink is actually a branch of WebKit, as WebKit is a branch of khtml.

Google's Chromium project has previously used WebKit (WebCore) as the rendering engine, but for some reason it has not ported its multiple-process architecture into WebKit.

Later, as Apple launched the WebKit2 and chromium of the sandbox design conflict, so chromium has been stuck in WebKit, and the use of porting methods to achieve and the main line WebKit2 docking. This increases the complexity of the chromium and, to some extent, affects the chromium's architecture porting effort.

For the above reasons, Google decided to derive its own blink engine from WebKit.