I also use tabs as a way to park a series of items for later consideration. It sounds like we really need a stack or queue for links (or we're treating the tab

I also use tabs as a way to park a series of items for later consideration. It sounds like we really need a stack or queue for links (or we're treating the tab bar as that). But the tab bar eats up resources (UI real estate if not memory). Thinking in terms of queue operations, my ideal UI would let me push tabs or links to a special bookmark folder, the queue folder. You could use menus if you had to, but to avoid menus, there would also be a mock tab permanently open that always displayed the next page in that queue folder. I could bookmark that displayed page to save it more permanently. I could close the page, which would remove it from the queue completely. Or I could send the page to the back of the queue. A queue folder like that would be persistent across sessions, but wouldn't load every single page on every startup. It'd be a bit like grouping all unread tabs by default, but also constantly storing that info in a folder as a backup, and having a really easy way to pop() tabs from that folder.