[jasode]

>Browser tabs were never intended to be used this way, bookmarks are.

The problem with booksmarks is that the tabs are not open. The booksmarks manager UI only show the title of the webpage but not what full page rendering is. Titles are often meaningless.

Of course, I could type in a better title when saving the bookmark... or... just simply not close the tab and consider it part of a "queue" to read later in a few days. It's lazier and easier. Plus the full page already completely rendered visually reminds me why I wanted to read it later.

For the webpages I consider as reference material, I do bookmark those.

[ocdtrekkie]

Why would you want hundreds of full page renderings open on your computer at one time while you're doing other things? I know browsers have since implemented optimizations to keep tabs suspended and reduce their performance hit, but I still don't understand why anyone would want this.

Would a screenshot being saved with your bookmark solve this need?

[jasode]

>Why would you want hundreds of full page renderings open on your computer at one time while you're doing other things?

For me, it's not hundreds. It's usually less than 50.

For throwaway content (not elevated to reference), the active tabs are easier to get to than navigating the bookmarks UI.

>Would a screenshot being saved with your bookmark solve this need?

It might help in some aspects but the core problem remains: the bookmarks UI is a separate area that I don't want to "manage" and that effort isn't worth it unless the webpage is promoted to reference status. Dozens of open tabs are just way easier and a more seamless experience. I often cycle through open tabs with Ctrl+PgUp and Ctrl+PgDn similar to cycling through active windows with Alt-Tab. Bookmarks UI don't have a "cycle" mode.