Data point: I often end up with many (read, ~100? Varies widely.) tabs open. I work like a priority queue. When I'm reading something, and see something inter

Data point: I often end up with many (read, ~100? Varies widely.) tabs open. I work like a priority queue. When I'm reading something, and see something interesting as a link, I open it in a new background tab and keep reading the current thing. Then go to the most interesting/relevant/time-sensitive tab I have open and read that. Repeat. ( while not que.isEmpty(): que.pushAll(que.popBest().getChildren()) ) This adds up quickly. For example, with HN I tend to browse the entire front pages (active / standard) / my user threads before I actually start reading links / comment pages. And when I'm reading a comment page I tend to open comments to reply to in a new tab to get back to them later. Ditto, if I'm coding something unfamiliar I often find myself looking up things recursively. Oh, here's two options to do thing A I need to do. Oh look, option A requires things B and C. Oh look, B requires D. This is sounding too complex, close tabs for things A/B/C and try option 2 instead. Etc. Realistically, I only need at max two or three tabs actually loaded at once most of the time - but at the same time I want things to be loaded before I get to them, and I do not want to lose data from unloading pages. Lazarus helps, but there are pages that still lose data on reloads.