I haven't used it so I have no idea. And all I've read is one comic about the architecture -- and while that comic is amazing, it still doesn't have every detail.

But I wouldn't be surprised if the multi-process architecture and the new JS engine turn out to make a surprising qualitiative difference in the performance of certain classes of JS apps.

Maybe so, maybe not. But even though I'm not writing anything particularly complex -- like, say, Gmail -- I've already had the thrill of working around situations where my one-lung JS interpreter is holding up the whole browser.

Heck, perhaps Gmail itself will be significantly smoother. Given the market penetration of Gmail, that would be a pretty good marketing hook for Chrome, all by itself.