Indeed. Around that era I had a fun little "crashmybrowser.com" toy site that had a few different JS tricks you could click that would absolutely wedge your browser (any browser, at the time). This had come after years of my being vocally annoyed that there weren't better guardrails around Javascript. Each of the functions was based on a real-world failure case.
Chrome was the first browser to be immune to all of those functions.
Mozilla really screwed the pooch not long after. Their biggest single misstep was forcing automatic updates in corporate networks. At the time, they still had pretty good adoption in the kinds of environments that had a couple of people somewhere deciding what everyone was allowed to run on the company computers. Chrome had already moved to forced updates, so these environments went to Firefox. When Firefox decided to follow Chrome, they no longer had that differentiation, and corporate IT had to choose between two browsers that both had automatic updates, but one of them had frequent memory and performance problems.
I've happily returned to Firefox a few years ago and don't have Chrome installed on any device I control.
Chrome was the first browser to be immune to all of those functions.
Mozilla really screwed the pooch not long after. Their biggest single misstep was forcing automatic updates in corporate networks. At the time, they still had pretty good adoption in the kinds of environments that had a couple of people somewhere deciding what everyone was allowed to run on the company computers. Chrome had already moved to forced updates, so these environments went to Firefox. When Firefox decided to follow Chrome, they no longer had that differentiation, and corporate IT had to choose between two browsers that both had automatic updates, but one of them had frequent memory and performance problems.
I've happily returned to Firefox a few years ago and don't have Chrome installed on any device I control.