[+] as in 500 or more. I use my browser windows to keep my 'state' of what I need to read and where I've left off, by the time they are all closed again I'm done preparing for an interview.
I could not get Chrome to stay stable enough with that much resource utilization, and the most important part I've learned is that Firefox's profiles storage formats are open enough that I've been able to recover from some pretty bad kernel panics (due to the graphics card switching on my laptop; disabling that fixed the panics).
Probably next Macbook Pro refresh cycle from Apple I'll upgrade to the latest they introduce, but Firefox-as-daily-driver has been able to take a lot of abuse from me.
So I've had to install an auto-reload extension[1] which simply reloads the Slack tab once an hour, and that contains Slacks stupidity.
Now Firefox is nice and fast, even with hundreds of tabs across many windows.
[1]: https://addons.mozilla.org/en-US/firefox/addon/reloadmatic/
Regarding performance on macOS, Firefox runs fine for me and I very very rarely have below 50 tabs open. Have you tried it recently? I had read there were some bugs with macOS but most of those were resolved a couple of years ago.
Firefox Mobile is generally fine, though I occasionally end up in a state where tabs refuse to load and I need to kill the whole app. Minor annoyance.
Desktop though, when I've got a bunch of tabs open and I close a bunch down by clicking the 'x's, I definitely notice how much Firefox speeds up as I close each tab. What drove the knife in was on the odd occasion that I needed Chrome, opening it up was like a breath of fresh air that was hard to ignore. Pages just seem to load faster and the Chrome seems more responsive under lots-of-tab situations.
Another part is peer pressure - the frontend guys all just use chrome, so pairing is a little bit more frictious. Though there is benefit to having someone in the team who uses something different to Chrome. I just don't want to be that guy.
What's wrong with the support it has? [1]
[1] https://addons.mozilla.org/en-US/firefox/addon/multi-account...
TBH, those days I tend to use separate browsers, because profile management is significantly less convenient than just running a different program.
And now they switched back to shared memory again, and the moment they did, the browser started hanging again, like it used to do pre-Quantum days.
Chromium's "per process memory isolation" is the right approach, despite all the cries about memory use. I'd rather have that than have the browser hang on me, or have more security issues.
If anything, I think even the future of operating systems is complete process isolation and separation by virtualization tech and encrypting each process in RAM with a different key. The hardware is coming, but it may take another 10-15 years for this to be fully realized.
I've seen numerous people craving for better container support, which is definitely a killer feature for people going forward towards a more private web. Why isn't Mozilla more actively developing this? Developers were the primary driver behind adopting Firefox during it's hayday - no reason why it can't be again if we have the resources to make a compelling case for it.