3 ms·

Actually, I'd like to revert the question: why would I close tabs? I generally have a few hundreds of them opened, because it works. Once in a while, I realize

by Yoric 9y ago

Actually, I'd like to revert the question: why would I close tabs? I generally have a few hundreds of them opened, because it works. Once in a while, I realize that I'm not going to read all of these things and I remove most of them. But I'm glad my Firefox scales up to these use cases.

falcolas 9y ago
> why would I close tabs Anxiety at the "I must read this" a bunch of open tabs can create. Frustration at being unable to find the tab I actually wanted to pull up out of the hundreds available to me. Forgetting something I actually wanted to do because it's buried in an avalanche of windows. It's kinda funny to watch a colleague who follows that mantra try and find the right tab, sometimes cycling through the 4-5 copies of the same website to find the one with the proper state. Then I see them do the same thing with terminal tabs/windows and cringe because they can never remember where they are or where their windows are connected to. Given that they have prod access and are connected out there while also developing locally, I'm sure nothing will ever go wrong...
- kodablah 9y ago
  That anxiety does not exist for everyone. I do a thing I call "immutable browsing" with tree-style tabs. I open EVERY link in a new child tab (and I might try to make my browser [0](shameless plug) support new-tab form submission). When I no longer need the parent, I just close it and other tabs move up. Navigating a tree of your actions or your current context is actually way easier than re-navigating a website. This is especially true with things like API docs where you might open a bunch of things and constantly re-reference them. Saving off trees and supporting a kind of quick-tab-find approach both help here too. This also helps when navigating things like source repositories on GitHub. We don't tell people to retrieve files externally because their filesystem makes it hard to find things. And we don't really chide people for too many editor tabs open either because we have a navigation panel. Why is a browser any different here? 0 - https://cretz.github.io/doogie/ https://cretz.github.io/doogie/
  - falcolas 9y ago
    > And we don't really chide people for too many editor tabs open either because we have a navigation panel > Why is a browser any different here? "navigation panel" In which case the tabs are effectively duplicated, and not of much use. > Navigating a tree of your actions or your current context is actually way easier than re-navigating a website. It really depends on the size of the tree, and the speed of page loads. For example, I keep a local copy of the Python, Go, and Boto documentation. This makes navigation fast and simple, even in the slowest of browsers. Click on a link, loaded (virtually) instantly. Hit the back button on my mouse, loaded instantly. One tab, fast as I could ever ask for. Ultimately, OP was asking why, I answered. No chiding intended, and only a little judgement - but disorder is incredibly ineffective.

by Yoric 9y ago

falcolas 9y ago

> why would I close tabs Anxiety at the "I must read this" a bunch of open tabs can create. Frustration at being unable to find the tab I actually wanted to pull up out of the hundreds available to me. Forgetting something I actually wanted to do because it's buried in an avalanche of windows. It's kinda funny to watch a colleague who follows that mantra try and find the right tab, sometimes cycling through the 4-5 copies of the same website to find the one with the proper state. Then I see them do the same thing with terminal tabs/windows and cringe because they can never remember where they are or where their windows are connected to. Given that they have prod access and are connected out there while also developing locally, I'm sure nothing will ever go wrong...

kodablah 9y ago
That anxiety does not exist for everyone. I do a thing I call "immutable browsing" with tree-style tabs. I open EVERY link in a new child tab (and I might try to make my browser [0](shameless plug) support new-tab form submission). When I no longer need the parent, I just close it and other tabs move up. Navigating a tree of your actions or your current context is actually way easier than re-navigating a website. This is especially true with things like API docs where you might open a bunch of things and constantly re-reference them. Saving off trees and supporting a kind of quick-tab-find approach both help here too. This also helps when navigating things like source repositories on GitHub. We don't tell people to retrieve files externally because their filesystem makes it hard to find things. And we don't really chide people for too many editor tabs open either because we have a navigation panel. Why is a browser any different here? 0 - https://cretz.github.io/doogie/ https://cretz.github.io/doogie/
- falcolas 9y ago
  > And we don't really chide people for too many editor tabs open either because we have a navigation panel > Why is a browser any different here? "navigation panel" In which case the tabs are effectively duplicated, and not of much use. > Navigating a tree of your actions or your current context is actually way easier than re-navigating a website. It really depends on the size of the tree, and the speed of page loads. For example, I keep a local copy of the Python, Go, and Boto documentation. This makes navigation fast and simple, even in the slowest of browsers. Click on a link, loaded (virtually) instantly. Hit the back button on my mouse, loaded instantly. One tab, fast as I could ever ask for. Ultimately, OP was asking why, I answered. No chiding intended, and only a little judgement - but disorder is incredibly ineffective.