As a reluctant user of tree style tabs (holding out for the restoration of tab groups), I disagree.
I usually have different sets of tabs open:
- A set for each of the 2-3 projects I have active this month
- Casual browsing
- Read later
- Do later
This adds up easily to one or two hundred tabs -- and these aren't bookmarks. Bookmarks aren't gone when you close the tab, which is the desired behavior for all the above cases.Pocket or similar (ignoring my refusal to use a 3rdParty service for my own data) would only be useful for do-later and read-later.
With tab groups I had a perfect setup which supported /all/ my use cases in one go. With TST I can roughly approximate this with a top-level tab for each (it's not great).
Bookmarks need to be replaced with something that covers a wider range of use-cases without having to cobble together a bunch of different workflows.
People know about bookmarks and pocket. Most people who are actively searching out extensions are not avoiding learning a different workflow (obvious if you think about it). I've gone through many different workflows, and I'll keep testing out more. Tab groups was the best thing yet for me.