Linked by Thom Holwerda on Tue 30th Jun 2009 15:56 UTC
Mozilla & Gecko clones As was anticipated, the boys and girls at Mozilla have released the final build of Firefox 3.5 today. Firefox 3.5 - originally supposed to be 3.1 - comes with many welcome improvements, chief among which is support for HTML5 audio and video tags.
E-mail Print r 12   · Read More · 63 Comment(s)
Thread beginning with comment 370867
To read all comments associated with this story, please click here.
Javascipt Speed
by boulabiar on Tue 30th Jun 2009 16:03 UTC
boulabiar
Member since:
2009-04-18

Javascript performance are not what I expect in this release.

They got a lot of time for this and it still not so good.

Have they compared it to Chrome/Safari ??

Reply Score: 2

RE: Javascipt Speed
by Kroc on Tue 30th Jun 2009 16:06 in reply to "Javascipt Speed"
Kroc Member since:
2005-11-10

Still not so good? Try using Internet Explorer.
Competition is tough with Safari, but Firefox 3.5 just makes Internet Explorer look even more like a complete relic.

For people switching from IE, the speed increase is going to be like night and day.

Well done Mozilla on a well organised release, an excellent product (that uses less memory than any other major browser) and open-video support.

Reply Parent Score: 5

RE[2]: Javascipt Speed
by sbergman27 on Tue 30th Jun 2009 16:32 in reply to "RE: Javascipt Speed"
sbergman27 Member since:
2005-07-24

...an excellent product (that uses less memory than any other major browser)...

I'll believe that when I see it. I will accept that FF has, perhaps, gotten "better", consuming memory somewhat less rapaciously than before.

Regarding relative Javascript performance, our previous discussions have left me with the impression that you have something of an anti-agenda regarding Javascript, as a reult of screen-reader technology having lagged so.

Edited 2009-06-30 16:32 UTC

Reply Parent Score: 2

RE[2]: Javascipt Speed
by gmlongo on Tue 30th Jun 2009 23:19 in reply to "RE: Javascipt Speed"
gmlongo Member since:
2005-07-07

"that uses less memory than any other major browser"

I'm assuming that you do not consider Opera a major browser since both Opera 9 and 10 use much less memory than FF 3.5.

Reply Parent Score: 2

RE: Javascipt Speed
by rkoot on Tue 30th Jun 2009 16:11 in reply to "Javascipt Speed"
rkoot Member since:
2006-01-03

that's comparing apples with pears.
chrome uses webkit and V8 for javascript, and mozilla uses gecko.
also, optimizations are not easy to accompish.

Reply Parent Score: -1

RE[2]: Javascipt Speed
by markob on Tue 30th Jun 2009 16:23 in reply to "RE: Javascipt Speed"
markob Member since:
2005-07-06

You can say Mercedes is faster than Fiat, can't you? Users don't care what engine browser uses.

Reply Parent Score: 1

RE[2]: Javascipt Speed
by kaiwai on Tue 30th Jun 2009 16:53 in reply to "RE: Javascipt Speed"
kaiwai Member since:
2005-07-06

that's comparing apples with pears.
chrome uses webkit and V8 for javascript, and mozilla uses gecko.
also, optimizations are not easy to accompish.


True, I ran the benchmark from here:

http://v8.googlecode.com/svn/data/benchmarks/v4/run.html

Firefox when compared to Safari is slower but with that being said, Firefox was designed to be easily portable when compared to the high optimised Javascript engine used in Safari (Squirrelfish Extreme) or Chrome (V8) which has alot of platform specific code which makes porting it to another platform (let alone architecture) not particularly easy.

With that being said, what ever optimisations that are being used one can't avoid acknowledging that Javascript is being pushed far beyond what its original purpose was - nothing wrong with that but there are limitations as to how much performance one can squeeze out.

Reply Parent Score: 2

RE: Javascipt Speed
by Erunno on Tue 30th Jun 2009 16:30 in reply to "Javascipt Speed"
Erunno Member since:
2007-06-22

TraceMonkey was developed in record time after both Nitro (formerly Squirrelfish/Squirrelfish Extreme) and V8 set the bar for JavaScript performance to new heights. I'm sure the Mozilla developers are content that TraceMonkey works correctly at the moment. Since Firefox 3.5 is out now I can imagine that the Mozilla developers will start to optimize TraceMonkey in ways which might cause a lot of breakage during development.

Edited 2009-06-30 16:31 UTC

Reply Parent Score: 2

RE[2]: Javascipt Speed
by Lennie on Tue 30th Jun 2009 18:03 in reply to "RE: Javascipt Speed"
Lennie Member since:
2007-09-22

For 4.0 they want to turn on TraceMonkey for the UI, which in comparison to other browsers is now slower, but this does allow for a lot of customization.

Reply Parent Score: 1