How Come All My Browsers Suddenly Suck?
theatlantic.com
theatlantic.com
But hey, at least it runs really fast sometimes!
a) Shorter release cycles and test phases b) More changes made in a release cycle without a corresponding increase in the number of testers.
It reminds me of the Internet Explorer / Netscape wars (around the time of Netscape 4).
I tried to use chrome but it always cries "Oh snap.." and all the tabs crap out (so much for individual). Firefox slows to a crawl, Safari and IE on windows both aren't even worth opening 1 tab in. So I stick with opera. It does the best overall job for lots of tabs. Although it takes quite a bit of memory..
With that said I really notice a lot of slowness on sites that use embedded fonts, more so then anything else. Next is flash, if I block flash from running my browser really speeds up. However Javascript has been replacing EVERYTHING. Even when it shouldn't it does, and is required by many sites, so I cannot turn it off, and some sites use a lot of resources for this mostly pointless js.
I use noscript to prevent anything from running that is not strictly necessary, but still, regular crashes.
Sure there are better ways to do it, but for less tech savy users a combination of browser windows and tabs are a good way to keep track of "thought branches". I do it sometimes, I google a topic (and open tabs) then when an interesting branch comes up I spawn a new browser window and then repeat the process again.
Why should lots of open tabs cause a problem? Worse case a browser should just unload them and pull them back from the cache when they are activated.
When pages were (mostly) static you could have 100 tabs on a slow machine and it wouldn't matter because they were mostly in the swap file. The more pages try and become active without a mechanism for the browser to "pause" them the bigger the problem lots of tabs becomes.
Tick: a person will load links in background tabs while they are reading because the pages don't load faster than the person thinks/reads
Tock: a person sees performance decrease and this reinforces the perception that loading in background tabs is a good idea
EDIT: I should maybe point out that I haven't any stability issues here though Firefox from time to time decides that it needs to become laggy(not Flash related).