Re:What’s Next for Multi-Process Firefox
by pcwalton on Tuesday August 02, 2016 @09:42PM
(#12214955)
> Multithreading is a disaster, it's just not a workable model for browser-scale applications.
All browsers, Chrome as much as any other, are heavily multithreaded, so this is clearly untrue.
Re:What’s Next for Multi-Process Firefox
by HelloImDumb on Tuesday August 02, 2016 @09:55PM
(#12215015)
Ok, you got me. What I said was nonsense, taken literally, I was being lazy; you're right, Chrome's heavily multithreaded too. But, there is process-level separation both between tabs/browser contexts with information of differing security sensitivity, and between nasty stuff like parsing and rendering versus basic UI etc. All the good defense-in-depth sandboxing that others have alluded to, that is the stuff of many papers.
It's freaking sad that Firefox is stumbling out multi-process in 2016. This has plainly been the way to go for years. Multithreading is a disaster, it's just not a workable model for browser-scale applications.
But hey, if they could recover Firefox from the ashes of the bloated disaster that Mozilla Suite became, I have hope that the community can catch up eventually. Maybe.