Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Tabs are not bookmarks. Use bookmarks.


Why should one use bookmarks rather than many tabs? I have many concurrent projects going, and things I refer to regularly, so I just leave them grouped in my tree of tabs on the sidebar. Much more efficient than digging through nested bookmark menus, or trying to make sure the bookmarks are properly classified.

Basically, my tabs are bookmarks, except tabs are integrated into the web-browser better.


So, the problem is that the bookmark UI design is broken.


My bookmark UI isn't broken: putting tree-style tabs in a sidebar is perfect.


If they would make the tree-style tabs very aggressively swap to disk, or even discard state entirely and seamlessly become a bookmark that would reload when clicked (perhaps this behavior could work only for white-listed domains, like wikipedia.org), that would be perfect.

The main usability problem with bookmarks over tabs AFAIC is that the bookmark UI does not encourage pruning bookmarks, so most become stale over time.

Another idea I've been kicking around for a while is "tab decay". Have tabs start to decay and close themselves after not being viewed for a configurable amount of time. 1 month would probably do it for me, it would save me a lot of cleanup time.


I'm saying that the description recommends using tabs in place of bookmarks because the bookmark UI is suboptimal.


> Why should one use bookmarks rather than many tabs?

Because, as the parent posts point out, tabs take up memory and can cause the browser to become sluggish.


Yes, that is true but there is no problem with just 60 tabs. I have 260 open tabs and my browser is not sluggish and the memory usage isn't too bad either, 3GB.


Bookmarks don't save state, which is especially annoying in a time where async calls are used so heavily.


And then we have people complain that their "un-used" tabs are taking up too much memory, so browser makers cut down on the level of state stored in the tab and that brings us to the current point.


So store the state on disk if the user hasn't been to the page for a while. When I've I last visited a tab three days ago I don't mind a little disk delay when I get back to it, in exchange for not having disk churn everywhere when I'm trying to get work done.


A URL should contain all of the state needed. If it doesn't then it's a poorly designed website.


URLs do not contain scroll position on the page.


Firefox has to work with the internet as it is, not the internet as we wish it were.


So do users. Keeping several dozen tabs open indefinitely decreases the stability of every browser. Computers have resource limitations. 95% of websites have bookmarkable links; use them.


Not Firefox, which is why I use it instead of Chrome. I am not saying tabs are without problems but they fit way better into my usage patterns than bookmarks.


This, I claim, is ideology.


> Use bookmarks.

Who said he doesn't?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: