Edit: For the folks who are apparently offended by my browser use, I’ll elaborate:
Why would anyone want a large number of tabs, you ask? Well, when researching a topic, it’s often useful to open in tabs, breadth-first style, every potentially relevant link in a network of {academic papers, historical web pages, wikipedia articles, ..}.
For me, it’s much more efficient to partition my browsing tasks into {open a bunch of tabs without looking closely at the content | go through the list of tabs in order, lightly skimming the content and closing any that aren’t relevant | dive deep into each relevant tab, reading carefully, taking notes, etc.}. I find that, as alternative strategies, both (a) trying to entirely finish with one tab before opening another, storing its hyperlinks in a text file for later examination, or (b) only opening links in the same tab, using the browser history as a linear linked list of my current place in the browsing tree, are much less effective.
Theoretically, my strategy could be done with a set of bookmarks, a list of links in a text file somewhere, one of those "read later" apps, etc. In practice, I find that it works better for me to just keep the tabs open in my browser. YMMV.
Anyway, now imagine you have 4–5 different long-term ongoing research interests/projects (possibly related). Sometimes, when diving into one topic, you end up stumbling across a useful tangent into one of the other topics you care about. Occasionally, the thing you stumble on is important enough to temporarily set aside the first topic (tabling the in-progress search by leaving all of the, say, 50 currently open tabs in their own window) and open up a new window to dive in on the second topic. Alternately, imagine you receive an important email, and need to suspend the entire research session for later. Again, it’s easier to just keep the window open with all the tabs in it, rather than closing everything and reconstructing it later.
This might not be the browsing style for everyone. But it works for me, and Safari is the only browser I’ve tried which holds up.
And only firefox has the infastructure to support such changes to its UI.
I would say that the only broweser that supports your use case is firefox, not safari.
This enables a workflow with several hundreds of tabs without the drawback of the additional RAM and CPU usage. Previously I shared the impression that Tree Style Tab for Firefox has ruined all other browsers for me and I could never switch away from Firefox but Tab Outliner showed me that I was wrong.
I typically have somewhere between 200 and 400 tabs open, and I work on a wimpy little 11" MacBook Air. The vast majority of those tabs are heavy things like Google Docs. Chrome seems to barely notice.
So why bother closing a tab when I can just switch out of the group when I'm doing something else? Another group does mail and google docs, another group does 'Atlassian stuff' (ticketing + wiki), another does build and CI, so on and so forth.
The only problem with this approach is memory consumption, because the modern web developer includes approximately 3/5ths of the entire internet on every page, and I 'only' have 8GB on my machine (non-expandable). Performance is fine for a while, but eventually (a couple of weeks) it starts to grind. Restarting FF at this point doesn't autoload the tabs, so it gives you a fresh slate, effectively.
https://addons.mozilla.org/en-US/firefox/addon/tab-groups-pa...
I use Chrome's profile feature, to have separate Google accounts signed in.
And my tabs tend to be in "clusters". E.g. I'll have one cluster (5-10 tabs) where I'm doing research on IPv6, another where I'll have a cluster on some JS, another on say, Python list performance etc.
I remember where each cluster is, and even some of the tabs within each cluster - so I just page quickly to that cluster if I know I need to retrieve that info.
Also, I tend to not be that disciplined when bookmarking or filing stuff - so there's that as well.
I'm still yet to find a good lightweight note-taking system - Confluence as a wiki isn't bad, but is still quite heavyweight.
There are probably more efficient workflows, but this one works fairly well for me.
Much of the time they are effectively a queue of things to review/skim/familiarize myself with while I'm authoring some code or a design doc. The ones with different favicons tend to be things like bugs where I owe an update, so I scan through them regularly (I'm extremely forgetful when it comes to lists of things to do).
Honestly I know how tree-style management would go for me: I'd group a bunch of things together in a tree and forget about them, largely defeating the purpose of having kept the tab open for me.
EDIT: uBlock or similar is absolutely must though, unless you browse only slim, "old-school" websites.
Just because the way he/she uses software doesn't work well with chrome doesn't make chrome bad software, and it doesn't mean the user is wrong. It just means that it's not a good fit for that person.
Your explanation there is a great example of what I personally want to see more of. A clear concise reason why you prefer one browser to another.
So often its just "X is faster" or "Y uses less memory" without any other details. And those kinds of complaints help nobody.