[othermaciej]

As one of the people who has worked on designing and implementing those changes, I can tell you that we did not need to change much in WebCore. And what we did do will probably be useful for Chrome's different multiprocess mechanism.

Incidentally, I would not say there is anything technically wrong or hacky about Chrome's process architecture. The reason we started anew is that it's not very reusable if you don't buy into the whole Chromium stack. Google chose to make multiprocess an app feature, we made it a framework feature. Reusing Chrome's code for a different app or another platform port would require inserting an API boundary where there was never meant to be one.

We did talk to the Google folks about whether they would want to integrate their multiprocess approach into WebKit itself, but that didn't really meet their needs or plans.

I do hope we can converge and share more over time.

[azakai]

Thanks for the additional info.

It does seem like this is mainly awkward for Chrome. But probably not a big deal.