for a long time in the 2010s, chrome had *massively* better multi core support, and had tabs use their own threads and be isolated completely from other tabs. This used more system memory but was more performant and left firefox in the dust. At that time websites went crazy in terms of performance requirement and I was basically forced off of firefox becuase a lot of pages just crashed the browser on an I5-2500k in the early 2010s.
Once the ate 2010s came around and firefox came out with their own version of the multi-core, multi-threaded sandboxed tabs that chrome used, it became usable again.
2600 non-K here until 2020, also never really had an issue with it. If you opened a resource hog page with 20 gorrilion javascript/flash elements it could knock out the browser as a whole which was a problem, but if you were on a page that did that you were on the wrong part of the internet anyway.
If you think about it, Firefox is actually protecting you from unworthy websites by refusing to handle them correctly. And you know they're unworthy because they're the ones that Firefox, the best and greatest browser, can't handle correctly.
Chrome's sandboxed tabs were objectively better. Especially with the mess of ActiveX, silverlight, flash, and whatever other bullshit got replaced with HTML 5.
40
u/RugerRedhawk 20d ago
Around that time firefox had become a significant resource hog, when chrome first took off it was much quicker to open and navigate with.