Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Given that you can only read from one tab at a time, why not have 103 (or more) bookmarks but only, say, 1 to 5 tabs open. What's the workflow? It seems obvious to me that if each page is a few megs in size and might have CPU taxing JavaScript etc that it's going to tie up a bunch of resources. Why not just open them when you need them?


> What's the workflow?

Tabs are my 'pending reading queue'.

1) Start investigating a topic. MMB the first few google results that look relevant/useful.

2) Ctrl+Tab. I'll be back to that google query in short order if they weren't.

3) Ctrl+W the first few results - they weren't useful.

4) Oh, hey, here's something. Read, scan down, and MMB 'future reading'.

5) Unread 'queue' (everything right of my current tab) is slowly growing. There will sometimes be duplicates. Read 'queue' that I want to keep open for reference / high level overview / branching off of (most things left of my current tab) also grows.

6) An hour later, I'm perhaps up to 50 tabs. Often less, but sometimes more.

Oh, here's a high priority question/bug/problem/task from my valued coworkers. I recall relevant documentation, but not the exact keywords. I open a new window, and repeat the process. Oh, hey, lunchtime! Interesting discussion over lunch prompts me to investigate another related topic. I open a new window when I return to the office.

Aha, results! A whirlwind of coding

Oh, end of day already? Hmm, I have 5 chrome windows open... LET THE HARVEST OF BOOKMARKS COMMENCE! Hundreds of tabs becomes 0 as I do a quick glance kneejerk yay/nay on bookmarking every one of them and doing some kind of basic organization by topic. Other coworkers use browser extensions to save their tabs instead, instead of engaging in this organization ritual.

The computers shut off. The lights go out. The sun has set, and silence descends, despite the open office floorplan.

...and then, some time later... a new day dawns...

> Why not just open them when you need them?

I don't want to wait for the webpage to finish loading when I switch to it. I don't have a clever way to rebind MMB to bookmarking new pages that I haven't even visited yet. I don't want my bookmarks cluttered with potentially useless tangent topics - I already have too many (thousands? tens of thousands?)

I have 32GB of RAM. I can spare a few gigs for Chrome.


Firefox works very good for me in this workflow. I have it set to open to previously open tabs and windows so that I don't have to periodically bookmark everything at the end of the day and Firefox doesn't crash on startup like Chrome if I have too many tabs open.

To better help me, I use the Tab Groups extension to group things into projects and used to use the Tree Tab extension to keep MMB tabs together, so that I can simply close all related tabs if I think that the topic I started MMBing on was not useful.

Current stats: 326 tabs, 1 window, 22 tab groups. 1.2GB of RAM spread across 4 processes.

[1]: http://imgur.com/a/8S77c


I have exactly the same workflow, and that's one of the reasons why I prefer Firefox, it uses much much less RAM when having 100+ tabs open then Chrome.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: