Linked by Thom Holwerda on Thu 23rd Sep 2010 21:36 UTC, submitted by google_ninja
Internet & Networking Now this is a subject sure to cause some discussion among all of you. LifeHacker's Adam Pash is arguing that Chrome has overtaken Firefox as the browser of choice for what he calls 'power users'; polls among LifeHacker's readership indeed seem to confirm just that. He also gives a number of reasons as to why this is the case.
Permalink for comment 442470
To read all comments associated with this story, please click here.
RE[5]: Tabs on top
by lemur2 on Fri 24th Sep 2010 11:02 UTC in reply to "RE[4]: Tabs on top"
lemur2
Member since:
2007-02-17

"The new benchmark indicates that Firefox 4 (with the new JaegerMonkey JavaScript engine) is more than 2.5x faster than the current stable version of Firefox 3.6.

Where is the problem with that?


Oh no problem there at all. I certainly can see Firefox catching up with the competition with their 4th release. I merely contest the claim that it will beat/already beats Chrome stable/latest "heftily."
"

Oh no problem there at all ... I haven't seen anyone make such a claim. Did you dream it?

Actually, I wouldn't have any problem if it turned out to be true eventually, I love to see vendors doing their best to outperform each other. I just don't see any evidence for the latter. You mentioned earlier that every vendor does this (ie publish benchmark that favours its own product). Microsoft was your example. That's my problem I expected better from the Mozilla folks, more honesty.


But it has already been pointed out to you, that Mozilla has been honest.

http://arewefastyet.com/

Results are plotted for the following javascript engines: moz JM+TM; google v8; apple nitro; moz JM and moz TM.

Each plot point is for the very, very latest engines on each day they are plotted, for all engines.

From the FAQ:
Who's behind it? Is Mozilla?

This site is maintained by Mozilla's JavaScript team.

What are the graphs?

The left-hand graph is Apple's SunSpider benchmark. The right-hand graph is Google's V8 benchmark suite.

Who are the players?

"JaegerMonkey" is the code-name for a new JIT being developed for Mozilla's JavaScript engine. Jaeger means "hunter" in German. "Tracing" is the original JIT. "Jaeger+Tracing" is them both turned on, working together. "Interpreter" is Mozilla's JavaScript engine without any JITing. "Google V8" is the JavaScript engine for Google Chrome, and "Apple Nitro" (aka JavaScriptCore) is the JavaScript engine for Apple's Safari browser.


How could it be any fairer, since they are using Apple and Google's own tests?

How could it be any clearer (they even give you a FAQ)?

Why do you keep insisting that Mozilla are not comparing the latest engines, when they actually are?

Sheesh!

That's my problem I expected better from the Mozilla folks, more honesty.


What more could you possibly expect from the Mozilla folks? They are using the oppositions own tests, and the very latest builds, and they are saying that under those test conditions, bent as far as possible to the opposition advantage, Mozilla aren't as fast yet.

It is perfectly, 100% honest.

What more could you possibly want of them?

Edited 2010-09-24 11:13 UTC

Reply Parent Score: 2