2 ms·
this + stuck js + single threading.. chrome's day-one multiprocess support was really the big shift since it allowed js bloat to not kill your session, which i
by cat199 9y ago
this + stuck js + single threading..
chrome's day-one multiprocess support was really the big shift since it allowed js bloat to not kill your session, which in turn allowed more js bloat to exist, which in turn made ff slower..
- staticassertion 9y agoYeah, when you think about Chrome's being selling points - a browser that won't crash just because one tab does, sandboxing, and responsiveness - it's literally all just from their multiproc architecture. It bought them so much to have that from the state. But, like Firefox, they now have a big codebase to maintain and it's not so easy to get massive perf improvements because changing up architecture is painful.