So for example, we want to make as many of the browser’s duties as possible run in parallel, so we can keep the main thread free for your application code. We want web applications to be as fast as possible.

In addition, this gives us an opportunity to do open-ended investigations into other performance improvement strategies. So, over the years, supporting multiple architectures has led to increasing complexity for both the WebKit and Chromium communities, slowing down the collective pace of innovation. The main reason is that Chromium uses a different multi-process architecture from other WebKit-based browsers. There are two main reasons why we’re making this change. Why is Chrome spawning a new browser engine? 1.12 Why is this is good for me as a web developer?.1.11 Opera recently announced they adopted Chromium for their browsers.

1.9 What should we expect to see from Chrome and Blink in the next 12 months? What about the long term?.1.8 Is this just a ruse to land Google-developed technologies?.1.7 What's stopping Chrome from shipping proprietary features?.1.6 So we have an even more fragmented mobile WebKit story?.1.5 Will we see a -chrome- vendor prefix now?.1.4 How does this affect web standards?.1.3 Hold up, isn't more browsers sharing WebKit better for compatibility?.1.2 Is this new browser engine going to fragment the web platform's compatibility more?.1.1 What sorts of things should I expect from Chrome?.1 Why is Chrome spawning a new browser engine?.

Chromium web browser engines