alt Hacker NewsNo need to be revisionist. Chrome brought amazing work to the table. The multiprocess, sandboxed system was incredible - it's not to say that Chrome was the first (IE did it earlier) but it was certainly way ahead of Firefox for a long time. Chrome is the reason we have Seccomp V2 on Linux. Chrome made "software is always up to date" the standard. Before Chrome, Blackhole and PoisonIvy absolutely ruined people's computers - click to play Java, click to play and sandboxed Flash, etc, were massive improvements to every day user security, probably some of the biggest security improvements to computers in my lifetime.
Firefox took a long time to catch up and their CEO was utterly incompetent, which seriously harmed Mozilla.
Replies
Chrome's multiprocess sandboxing wasn't unambiguously good. It carried a steep cost in overhead.
Back when Chrome was new, you could run Firefox with a decent selection of add-ons to get security benefits of similar magnitude through different mechanisms. The NoScript extension was at the forefront, providing a lot of functionality way beyond just blocking JavaScript per domain. And Firefox with extensions always had better privacy controls.
> Firefox took a long time to catch up and their CEO was utterly incompetent, which seriously harmed Mozilla.
This is basically whole history of Mozilla and to be honest most of open source projects that dont have BDFL type of leadership.
I remember for a while that Firefox had a single process architecture for all tabs. This often frustrated me as one bad tab could just crash the whole browser while Chrome used separate processes for each tab, prompting me to switch to Chrome for a bit. Firefox caught up ages after chrome, and now I went back to them over the manifest v2 stuff.