The More Popular the Browser, the Slower It Is
demishade writes "Peacekeeper, the browser benchmark from the makers of 3DMark, comes out of beta and shows an interesting (though perhaps not surprising) tidbit — the more popular a browser, the worse its performance. While it should not be surprising to anyone that IE slugs at the last place, the gap between Firefox and Chrome, is. Once IE's market share goes the way of the Dodo will web developers start cursing Firefox? How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function?"
Here we are on the Slashdot plains in Africa, looking for that most elusive of species, the First Post...
Chrome was designed with JavaScript performance as a top goal. So why are we surprised it performs well?
"No matter where you go, there you are." -- Buckaroo Banzai
How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function? It already exists, in the form of http://www.chromeexperiments.com/
No - Lynx is!
Do the words "TraceMonkey" mean anything to the authors? It's the core Javascript engine of the upcoming revision of Firefox. And it is fast. Some benchmarks suggest that it is highly competitive with V8 (Chrome) and SquirrelFish (Safari).
(Speaking of which, isn't it a bit disingenous to compare Safari 4 BETA to the current version of Firefox? Why not compare the Firefox beta then? Smells of yeller-bellied journalism to me.)
Javascript is currently a hugely competitive area. Every browser revision is trying to boost performance. (Including Microsoft.) It only makes sense that the older and cruftier engines would have a harder time competing with the newer and more nimble engines created by these upstart competitors. However, with the exception of Microsoft who's stuck updating JScript (haha, bundle FAIL!), all the other competitors can and are swapping out engines for faster and faster performance.
Javascript + Nintendo DSi = DSiCade
Features create popularity, and popularity pushes for more features as users cry that the next browser over has something it doesn't. This create bloat.
Then again, over time, isn't this what happens with almost all software? They get more and more features as time goes by, and get bigger and consume more resources. Look at the size/requirements of any linux distro with a graphical system over the past 10 years.
No one wants to lose features, and users complain too much, so the only way to get a faster thing with less features is to fork it, or start anew (which is what the lesser popular browsers have often done).
Tibbon
tibbon.com
Javascript performance still doesn't matter for most users, and power users largely have Javascript disabled or blocked. Maybe Google needs to release a killer app that relies on Javascript and has borderline performance on anything slower than Chrome.
When we're just talking about loading web pages, no one is yet within shouting distance of FF with a good Adblock filter list.
JS benchmarks seem somewhat pointless for now. 99% of what we do on the web happens instantly (if you have a low latency connection) on all browsers if we stop the ads from loading.
"I zero-index my hamsters" - Willtor (147206)
It's so unfortunate that researchers these days don't realize that correlation can easily be a coincidence, and not a real relationship between two variables. It is especially unsuited in this case given the tiny number of data points and, oh, the convolution of these results with other factors like OS bundling (Windows/IE) and time on market (All 3, most significantly Chrome).
A more interesting (and likely actually related) set of data would be browser performance vs. market growth rate. Where are those numbers?
Also, web developers don't curse IE because it's slow. In fact, many pages are still static and don't feature nifty DHTML tricks, so the slowness of IE has no effect on the page at all. We web developers curse IE because it's not standards compliant and because making both the CSS and those nifty DHTML tricks WORK in IE is like eating barbed wire. Firefox has acceptable Javascript performance and is mostly standards compliant, and the existence of the Firebug plugin makes it invaluable as a web developer's test browser. I don't think web developers will curse a browser like Firefox for slow Javascript performance like we curse IE for violating all the standards.
These guys are idiots.
It's obvious that the last letter in the name being a vowel has more to do with performance than popularity.
from low to high performance - a,e,i,o,u
This just in: People don't choose their browser based on Javascript performance alone.
I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
Nope.
Sitting in front of my computer imagining webpages is even faster.
And probably better then using lynx
The Kruger Dunning explains most post on
I do, however, agree with another poster who pointed out that it's odd that Safari was the only beta included. If they'd included Opera and Chrome's preview releases they'd have scored 100 on the Acid3, and potentially higher on the speed tests too.
Telnet's here, boys. What say you now?