3 ms·
What’s the thought process behind closing them? Using tree style tabs I have a forest of tabs. I am working with lots of ‘web apps’ (currently mainly the AWS co
by tokamak-teapot 7y ago
What’s the thought process behind closing them? Using tree style tabs I have a forest of tabs. I am working with lots of ‘web apps’ (currently mainly the AWS console) and closing tabs would mean having to go and find the particular resources every time I want to work with them. I probably hit each of around 50 tabs - across two or three windows - an average of 20 times today. Then there were dozens of ephemeral tabs too.
- webmobdev 7y ago> What’s the thought process behind closing them? - Why keep a site open when you are done with it? - Too many tabs and it gets difficult and irritating to find and open the site you want. - Have never needed to keep many, many sites open in the first place.
- SAI_Peregrinus 7y agoNot the person you're replying to, but may as well answer since I also use tree-style tabs similarly. > - Why keep a site open when you are done with it? Why assume you're done with it? I have a number of tabs just for Grafana dashboards I'm monitoring. Re-finding the particular configuration from the home page every time would be annoying, bookmarks would require reloading the page (and thus re-running the slow queries that happen on load instead of on data update), etc. > - Too many tabs and it gets difficult and irritating to find and open the site you want. That's what tree-style tabs solves. Tabs are a hierarchy, just like bookmarks or folders normally are. It's much easier to navigate. > - Have never needed to keep many, many sites open in the first place. I've got email, calendar, a bunch of Grafana tabs, plus a few datasheets, a schematic, Jira, Confluence, and Github. And that's just for work, for news I tend to open articles in tabs with HN comments in child tabs and then go through & read them in sequence, but I keep work & non-work in different windows.