Google congratulates everyone with the day webmasters new rendering engine
Of course, in the US, webmasters didn’t come yet another day, but the Internet giant prepared for the holiday perfectly well , with a characteristic cynical sense of humor (the news of the closing of YT on April 1 clearly demonstrates this). So, meet: Google Blink - a fundamentally new rendering engine for Google Chrome.
Since there is enough sarcasm for today, then to the point:
You can, of course, consider the reason for the transition, that WebKit has a major defect - it was not made by Google, but Adam Barth, familiar to many of WebKit’s many commits, reports that the fact is that Chromium’s multiprocessing model has become too complex to pull the Legacy code from the main WebKit, so it was decided to finalize the engine. In the process of getting rid of legacy, 4.5 million lines of code were thrown.
Key points of interest to developers:
Details in the record of the developers Chromium .
Bug tracker remains standard from Chromium .
Pick-compile here .
If you fired up using Blink in your projects, then there is a slight disappointment, because the engine is too tightly tied to the Chromium code base, so without it Blink is practically useless. However, it will be possible to use the lightest Chromium Embedded Framework .
PS Linus Upson, known primarily by Google V8, said that the name of the engine is also not just so chosen.
The blink tag was one of the worst tags embedded in HTML, so we called the engine by tag name, which is not supported by the engine. For example, we called our flagship Chromebook Pixel, because we wanted to make the pixel invisible. So many web development veterans will remember the past and laugh at what is finally gone.
Since there is enough sarcasm for today, then to the point:
- Blink is an open source engine, whose main container is, of course, Google.
- Blink is essentially the same forked WebKit. Google has already replaced the lion's share of Apple WebKit's upstream from Upstream (the same V8, Skia, network stack is missing in the upstream), so replacing the engine itself is an expected move
- For web developers, they promise that they won't even notice the transition at first.
You can, of course, consider the reason for the transition, that WebKit has a major defect - it was not made by Google, but Adam Barth, familiar to many of WebKit’s many commits, reports that the fact is that Chromium’s multiprocessing model has become too complex to pull the Legacy code from the main WebKit, so it was decided to finalize the engine. In the process of getting rid of legacy, 4.5 million lines of code were thrown.
Key points of interest to developers:
- Google will not use proprietary prefixes for the specifications being developed. The spec will be used by Blink developers without a prefix, but hidden. To activate, you will have to include a spec in the experimental parameters, or via the command line
- The introduction of new HTML / CSS / JS specifications will be carried out in accordance with the Chromium function panel.
- The new engine will allow the Googleers to introduce a feature that allows you to run parts of the same page in different processes
- Migrate DOM to JavaScript. In theory, DOM should become much faster than WebKit itself.
- Finally, they will deal with memory leaks by removing the ScriptValue / ScriptState abstractions that WebKit needed for two different JS engines.
Details in the record of the developers Chromium .
Bug tracker remains standard from Chromium .
Pick-compile here .
If you fired up using Blink in your projects, then there is a slight disappointment, because the engine is too tightly tied to the Chromium code base, so without it Blink is practically useless. However, it will be possible to use the lightest Chromium Embedded Framework .
PS Linus Upson, known primarily by Google V8, said that the name of the engine is also not just so chosen.
The blink tag was one of the worst tags embedded in HTML, so we called the engine by tag name, which is not supported by the engine. For example, we called our flagship Chromebook Pixel, because we wanted to make the pixel invisible. So many web development veterans will remember the past and laugh at what is finally gone.
')
Source: https://habr.com/ru/post/175377/
All Articles