| > I don't really think it would work as well for the "tab collectors" as they think. I’m a collector and it’ll definitely help me a lot in one specific use case: I have a ton of tabs open and want to close some of them, but not all of them Very often I’ll be growing the tab count on one subject (usually because I can’t find a satisfactory answer), finally I’ll piece that answer together and start applying the new knowledge elsewhere... then come back to my browser and all those extra tabs are now useless, but I can’t tell where they start or end Sometimes I can find the “root” (the point where I started opening tabs on that subject) and know I can safely close everything to the right. But sometimes other important things are mixed in, so it’s not always possible, and even if it is that still means I need to find the root The usual solution is having to cycle through every tab, take on the cognitive load of having to identify whether the tab only applied to that subject or not, then close it or keep it Sometimes that means evaluating the relevance of 30 different tabs of 30 different sites that all look different, and rarely do they have “SUBJECT X” printed at the top It’ll be really nice to be able to just close the group and not think about any of it and not worry about whether I closed something important, I’m really looking forward to this feature |
You're right that cycling through tabs and making individual decisions on closing each one has a high cognitive load. Closing an entire window is much easier.
A while ago I realized this, and started to front-load that cognitive effort and make sure that the "root" of each "subject" gets opened in a new window (or at least detached early enough once I realized that I was branching off into a new subject).
An example of the root of a subject could be an item in an issue tracker, and that window could also contain tabs for code search windows, Google searches on that topic, Stack Overflow answers, etc. Once I'm done fixing the bug, I just close the entire window/subject/group, without thinking about each individual tab.
The front page of HN is also usually the root of a subject. I'll open tabs for articles and comment pages, and then close the whole window once I'm done with my break and want to go back to work. If there's something particularly interesting that I want to save for later, I'll detach that tab and close the rest.
For the C++/RAII people, this is kind of like making sure that every object has an owner, and that memory is freed when those objects go out of scope. This is a lot easier than manually doing a mark-and-sweep over all your tabs :)