IMO just one good new tab UI over a user's history/local cache could make a sizeable dent in Google's ad revenue
Try it, then read the original post and the comments again. :)
I think this is the missing piece on all this discussion.
IIRC pocket has had some serious vulnerabilites exposed.
If i don't look at a tab for a few hours, it's not worth keeping around as it just adds to the noise without providing value. If i need to read something, i either read it immediately or bookmark it to read later. The result: i can confidently resume work without distractions at any time.
> You can't just glance at the top of the
> browser to remember where you just were.
With tree-style tabs, each root represents a train of thought. I just collapse them until I decide what to do with them. Sometimes I bookmark and banish them. Sometimes I come back to that thought next weekend.
Chrome's default tabs at the top, to me, are the distraction where each tab has equal weight. But I'm not going to say that anyone is doing it wrong if that's what they prefer.
In this particular example microsoft uses edge to push people to use the latest version of their adware/spyware OS.
Neither the back button nor bookmarks retain state sufficiently or have sufficient responsiveness to replace open tabs.
I have 2-3 tabs open most of the time. If I am looking something up, I go to 10-12. When I am done, it goes back down to 2-3. I can't even fathom under what situation people are using hundreds of tabs.
I have heaps of tabs open, but there are orders of magnitude more pages in my browser history. The latter usually contains so much that is too much to look through to find anything but quite recent entries. The tabs still open are pages still with some relevance to me, while the history is filled with lots of incidental stuff that is no longer of use.
[Edit: also, with open tabs the page content is already there so it's more quickly accessible. This can be useful if you need to look at it to help find the page you're looking for, and to get the content from the page]
For me, it reduces cognitive load. I don't keep in mind all tabs that I have open -- that's why I keep them open! To forget about them.
Bookmarks are mentally for things I want to save and reuse. But I'll probably open 40 HN sourced articles (from the main page and comments) per day, and continually cycle/review them for interest/effort throughout the day.
I also close tabs as soon as I'm done with them which is why I only have 150-200 tabs open. Each categorized by activity, so when I switch one activity to the other I save time and cognitive load by having them right as I left them instead of having to find what URLs to reopen and actually open them. This way I only have 5-30 tabs open in front of me while the other are offscreen in other groups.
If browsers had a sort of tab queue where longer lived stuff then things could be a bit better on this front I think
To me, the problem is that bookmarks are "while browsing, go to a different component that loads the browser tab with what I want".
Tabs, OTOH, are a placeholder for things that I want to keep just 1 step closer.
Saying it that way, I don't think it makes rational sense. But 1 cognitive step to a page instead of two is huge for me.
https://chrome.google.com/webstore/detail/holmes/gokficnebmo...
A better history may solve their problem.
First you have to create some categories, but that doesn't take long and then you simply throw bookmarks in these categories. the end.
I think the main lesson is that bookmarks don't work too well or people just don't use them. If nothing else, make the bookmark display show newer bookmarks rather than the same old ones from four years ago. And maybe start preloading if they are opened regularly. Merge two features together, maybe add optional other organizational features for example similar to new tab screen.
The tricky thing is that there are a lot of things that are potentially supposed to happen while a tab is open. The browser is now it's own OS, and it may be very difficult for developers to use important features if tabs (processes) only _look_ like they are running.