I use Chrome, you know why? Firefox, even stripped of plug-ins etc is a SLOW ASS BITCH.
Seriously, I go to a lot of script-heavy sites (goddamn sploicers, err, I mean art sites) and the only thing that doesn't make it pure pain is Chrome. Quicky, easy, you get in you get out.
There's a lot of stuff I don't like but, it's fast so it wins.
I used to be a plugin junkie, but really I can use other programs for a lot of that stuff.
I've managed to find a problem in the latest stable Chrome release (actually, it's in the underlying WebKit, so Safari will have the same problem). What's this problem? Well, on pages that are a bit larger, with scripts running that access data that is sent in different chunks, Chrome grinds down to a measure-in-minutes-instead-of-seconds speed.
It's been reported to Google
here and
here. Here's my scenario:
I have a page with a grid with a dropdown list of values for each row in the grid. Normally, this would mean a large amount of HTML in the page to tell the dropdown lists what values to have in their lists. I need to reduce page size, so I use Javascript to load the values into the dropdown lists after the page loads.
When there are only a few values to load, this runs fast (300k page loads in ~2.4 seconds, including running said Javascript). As soon as there are more than twelve or so values to throw in the dropdown lists, this runs horribly slow (same page loads in ~157 seconds, running said Javascript for about ~141 seconds of that).
What I've learned is that browsers get sent web pages in chunks of data; once all the chunks arrive, the page will have been completely downloaded. Looks like Chrome starts rendering and running Javascript before all the chunks arrive, causing a lot of re-rendering and re-running the Javascript, in turn causing a horrendous slowdown (in my case about 65 times slower). Also, this seems to be a Chrome 4 issue, not present in Chrome 3.
Firefox and Internet Explorer may be slower, but I haven't encountered these kinds of bugs creeping into either of them. Probably because they're not pushing their new versions out quite as fast - Google seems content with occasionally breaking its software.