Skip to content

Comment on Chrome's Process Model Explainedparent

Comments

Much of the code is shared with non-multiprocess ports, and many of the leading WebKit ports have been building a WebKit2 port.

It may even lead to more uniformity, if we can share at least some of the approach to multiprocess with Chromium.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.