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?"
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
If you look at it from a popular/performance perspective, you are going to find that, generally, the newer software is better performing, because that is a selling point above the competition. It will also be the least popular because it is newer.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
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.
"How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function?"
Ans: never
because 80-90% of the market will choose not to
bother with that application because they don't
know how to DAU-EN-LODE and install a different
browser.
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..
You just described IE.
But you lost me here.
Game! - Where the stick is mightier than the sword!
I've heard a lot of talk about Javascript performance as intensive Dynamic HTML applications become mainstream.
Most of the apps I seen really don't have that much Javascript when you compare it to the amount of code that is in your typical desktop app or server side application. And ultimately many of the functions are small.
What I've noticed is instead their is a difference in the rendering engine itself. Javascript might be a single line to change the CSS of an element or change the visibility attribute, but then the browser takes forever to collapse the item...or the CPU spikes when some huge element of a big page disappears and the whole page has to move over/up/down.
Are we really talking about how fast the DHTML engine responds or is Javascript really that stinky slow that changing the element underlying take a while. I'm not sure I care if calculating primes in JS could made faster. Isn't most of Javascript just mapping down to a C++ library below it?
No, those are the ones that are popular. What people don't like are browsers that adhere strictly to the standard when the web is full of pages that don't.
Rethinking email
Also, popularity tends to impede progress. The more people are using a software or hardware product, the more you have to lose by breaking compatibility with old version or doing something zany. Meanwhile, more obscure products have a greater need to do something a little zany in order to carve out their niche.
I'd use a desktop application.