Also from a scaling perspective I wonder if its linear with tabs. There are various tribes of tab users and if its linear, a "normal user" who uses about 3 or so would scale down to approximately nil.
Also from a scaling perspective I wonder if its linear with tabs. There are various tribes of tab users and if its linear, a "normal user" who uses about 3 or so would scale down to approximately nil.
That's a reasonable conclusion only if people are aware that they're making the trade, which I suspect most users are not (otherwise this article would be rather boring)
I think low-memory situations are the most likely explanation for slowdowns experienced by typical home or office users.
It's very much a paper analogy, highlight the interesting bits, add new stuff to the 'to read' stack, and when the 'to read' stack is empty you're done and the notes file contains the extracted information.
The note taking extension I use is called scrapbook and I couldn't live without it. I also use vertical tabs which makes it much easier to work with large numbers of tabs.
https://wiki.thingsandstuff.org/Main_Page
Edit:
also https://github.com/343max/TabHibernation great to save resources when processing too many tabs. also, https://chrome.google.com/webstore/detail/session-buddy/edac... for snapshots in case you do crash
otherwise, Readability
Tabs are sort of a halfway house to bookmarks for me. They persist across browser restarts, but the fact that they are still open increases the chances that I'll consume the information in them.
My solution was to add a 8GB stick of RAM with the usual disabling of javascript by default, no iframes allowed and no flash installed with adblock and fanboy's lists.