I like Vivaldi, but I'm having major problems and I have major suggestions
@anamon There must be an easier way to do that, maybe RSS feeds or a web crawler that works online instead of on your local machine? Sounds like you spend 10 to 12 hours reading stuff that could be summarized in minutes in another manner. Maybe using a backhoe with a jackhammer attachment instead of a pick & shovel..
paul1149 last edited by
600 tabs, IMO, is stretching the limits of the usability of the GUI, and would be doing the same to the computer hardware, were it not for Vivaldi's ability to hibernate idle tabs and not open existing tabs until they are given focus.
Perhaps a tab organizing extension would be good for you.
The stacking function is a very good step forward, but there is plenty of room for improvement in it at this point.
@dleon Succinctly put, Thank you.
Marko Indaco last edited by
@fixitmanaz I don't think there is a more efficient way. As I tried to explain, when I work this way, the overhead of handling all those pages and tabs is at an absolute minimum. If I see a link that I want to look into, I middle-click it and it immediately opens in the background, without stopping my browsing the list, or whatever I'm doing.
For example, I can go through a newsletter of new music releases that contains links to 300 new records. I will have the 50 that seem interesting to me opened up in background tabs pretty much as fast as I can even go through the newsletter. I don't think there can be a faster way of "remembering" these URLs than this. Likewise, when going through the tabs, it's a matter of one click, or Ctrl+W, to dismiss one and automatically jump to the next. I go through the tabs practically as fast as I can make the decision.
Yes, I sometimes might spend 10 hours reading or browsing stuff in this fashion, but 9h50 of that will be pure reading time. I don't spend time managing bookmarks or working crawlers. My hundreds-of-tabs sessions can sometimes last for several days. I work alongside them in other tabs, and whenever I have a little time, I work through a few dozen tabs I "remembered". I honestly don't think I could come up with a more efficient solution, as long as the browser performance plays along.
Sorry for reviving a stale post, but wanted to support @Anamon and others, arguing for modern browsers supporting powerful tab managers. And apologies in advance to the "don't have time for these long posts" people, this is a mini version of the OP's
TLDR: 1. tabs are the browser's units of work; 2. many people juggle lots of work; 3. extensions have shown us that organizing lots of tabs effectively is possible; 4. any browser that wants to be part of the future of work needs to catch up.
I agree with another poster too, that claiming a person shouldn't work in a way they find effective, is not constructive in a discussion about productivity-tool development.
Conceptually, tabs, tab history and bookmarks all exist on a continuum, even though we think of them as being different types of things. And certain tab management methods, those that allow us to avoid drawing arbitrary past-present-future lines on our work plan, unlock powerful productivity.
There is no reason (other than "it's hard to design a good tab management system") for siloing work into different modalities like "opened but didn't view yet," "still working on it," "saw but didn't save," "saw and saved and closed," and "saw and closed but didn't put away."
Firefox had been my go to browser for long past its shelf life, simply because it had the Tree Style Tabs extension, which allowed easy management of hundreds of tabs, past present and future, into topic- or project-organized sets.
Now that I use Chrome, I stick with it long past its own shelf life, simply because nothing manages tabs and windows like Tabs Outliner. It's solo-developer quirky, and I wish a big team would tame it's UX, but I would be much less productive without it.
I always have four or five thousand tabs organized. I use three levels: per chrome login to get an instance of Tabs Outliner for each of my companies, then by project into windows, and by task into tree branches.
They are hibernated when I'm not using them, they don't open on browser launch, and overall there is no significant impact on the browser, as long as one remembers to put away work when switching projects.
Since 99% of them are really just lines-of-text placeholders, organized topically, claiming that one "shouldn't have many tabs in the first place" is kind of like saying "it's bad to have many documents tucked away in project folders in the file cabinet in your office."
For me, the browser is my office. Seventy percent of my tools have web interfaces. "Don't keep very many tabs" is pretty much the same philosophical position as "an empty inbox or task list means I'm more productive."
For all three cases, I agree with Google (don't bother to delete any emails, storage is virtually free and you may need to look at them again) and Marissa Meyer "Look, I just make a to-do list every day in priority order from most important to least important and celebrate the fact that I'd never get to the bottom of it, because if I did, I would have spent a bunch of time doing relatively unimportant things."
I check in with Vivaldi's tab management system development every month or two. It's getting really good! But it still has a long way to go, to pry me away from a much-worse browser with a much-better tab manager.
I can imagine that it might be possible to let Tabs Outliner sit inside a web panel in Vivaldi. That I'd like to see!
For part of the OP's core complaint: just setting up lazy loading on launch should fix the "browser hogs 100% of my network bandwidth for ten minutes trying to open six hundred tabs all at once" problem
Pesala last edited by
@brucetm If it takes more than 500 words to make a point, people will skim read it and miss much of what is being said.
One can be too concise too, but if you want people to take notice, don't ramble.
@pesala Thank you for the advice. The TLDR at the top was for for you. The rest was detailed feedback about this feature and use cases, for the devs.