<story><title>Scalability</title><url>http://gregor-wagner.com/?p=79</url></story><parent_chain><item><author>Flam</author><text>I&apos;m afraid I disagree.  There&apos;s no way you could multi-task all 30 open tabs at the same time.  Read what you need and close the tab when you&apos;re done.  Leave only the topmost page of the documentation open so you can find your way back down again if you need to.  You should be able to tell whether a page has value to you or not within the first 30 seconds of skimming through it.  Do you open every result on google for the first 3 pages of all your searches or something?  Baffling.</text></item><item><author>cbs</author><text>How you feel doesn&apos;t really matter when you&apos;re doing anything other than idle browsing.&lt;p&gt;This morning I had about 30 tabs open when I came into work, all documentation or reference of some sort that I will use in the next few hours.  And thats about the lowest I ever get, if I&apos;m looking up something new to me or complex it will easily shoot over 100.</text></item><item><author>Flam</author><text>W.T.F.
I can&apos;t go over 6 without feeling messy.</text></item><item><author>rmccue</author><text>&amp;#62; The real question is whether you would ever have that many tabs open, and how much memory do you have on your desktop?&lt;p&gt;I have 60 tabs open now (in FF), and this is after closing most of them, on a 32-bit system with 4GB of RAM. I regularly hit over 200 tabs when browsing.</text></item><item><author>tytso</author><text>Performance is the side-effect, not the cause.  The cause is the fact that chrome uses separate processes both for security, and so if one tab crashes, you don&apos;t lose them all.&lt;p&gt;The fact that it uses more memory is a design tradeoff (although with shared text pages it&apos;s not as bad as one might think).   The real question is whether you would ever have that many tabs open, and how much memory do you have on your desktop?</text></item></parent_chain><comment><author>dredmorbius</author><text>It&apos;s called context / state.&lt;p&gt;The more state I can leave up on my desktop, the better.&lt;p&gt;If there were better management within the browser -- non-visible tabs were eventually unloaded, with any page-state (forms data, etc.) saved -- then you wouldn&apos;t have the memory bloat problems that occur.&lt;p&gt;The thing is that it&apos;s a very large virtual workspace to spread things out over. So long as it&apos;s organized, it&apos;s really useful.&lt;p&gt;Look to movies especially of researchers in the 1970s or 1980s who&apos;d spread clippings and papers over all horizontal surfaces in an office, tape/pin them to a wall, etc.  You want to be able to scan quickly through the space at eye-speed, not have to dig into files / organizers / storage / regenerate the information every time you want to look at it.&lt;p&gt;It&apos;s why you&apos;d rather have a large monitor -- you can strew windows over it and see more, rather than have to manage windows and go through them repeatedly.</text></comment>
<story><title>Scalability</title><url>http://gregor-wagner.com/?p=79</url></story><parent_chain><item><author>Flam</author><text>I&apos;m afraid I disagree.  There&apos;s no way you could multi-task all 30 open tabs at the same time.  Read what you need and close the tab when you&apos;re done.  Leave only the topmost page of the documentation open so you can find your way back down again if you need to.  You should be able to tell whether a page has value to you or not within the first 30 seconds of skimming through it.  Do you open every result on google for the first 3 pages of all your searches or something?  Baffling.</text></item><item><author>cbs</author><text>How you feel doesn&apos;t really matter when you&apos;re doing anything other than idle browsing.&lt;p&gt;This morning I had about 30 tabs open when I came into work, all documentation or reference of some sort that I will use in the next few hours.  And thats about the lowest I ever get, if I&apos;m looking up something new to me or complex it will easily shoot over 100.</text></item><item><author>Flam</author><text>W.T.F.
I can&apos;t go over 6 without feeling messy.</text></item><item><author>rmccue</author><text>&amp;#62; The real question is whether you would ever have that many tabs open, and how much memory do you have on your desktop?&lt;p&gt;I have 60 tabs open now (in FF), and this is after closing most of them, on a 32-bit system with 4GB of RAM. I regularly hit over 200 tabs when browsing.</text></item><item><author>tytso</author><text>Performance is the side-effect, not the cause.  The cause is the fact that chrome uses separate processes both for security, and so if one tab crashes, you don&apos;t lose them all.&lt;p&gt;The fact that it uses more memory is a design tradeoff (although with shared text pages it&apos;s not as bad as one might think).   The real question is whether you would ever have that many tabs open, and how much memory do you have on your desktop?</text></item></parent_chain><comment><author>sjs</author><text>We don&apos;t &quot;multi-task all 30 open tabs at the same time&quot; whatever that means. Just like you can have many apps running but maybe only one or two windows visible at any time, you can have many tabs open and only focus on one or two at a time.&lt;p&gt;For those of us who write software being able to discretely switch to a certain doc with ctrl-tab or ctrl/cmd-# is much quicker and efficient than navigating N times throughout the day just to reduce the # of tabs.&lt;p&gt;If I&apos;m working on a Twilio web app I might refer to the Twilio docs, Ruby docs, twilio-ruby source, and some web related docs all throughout the day (HTML/JavaScript/CSS). Oh yeah, don&apos;t forget the JavaScript library docs. Why look them up each time you need them? Open them at the beginning, close when you&apos;re done work and that&apos;s that.&lt;p&gt;Your tab related OCD shouldn&apos;t enter into our workflow ;-)</text></comment>