Cru_N_cher wrote:http://js1k.com/demo/653 (almost freezes the GUI, shows nicely how heavily firefox needs seperate GUI processing like GChrome has it)
In an m-c build, yes. In a JM/TM build, not here....
http://29a.ch/2010/6/2/realtime-raytracing-in-javascript
Yeah, there's serious memory thrashing going on here. See analysis in
https://bugzilla.mozilla.org/show_bug.cgi?id=590379 from a few weeks ago.
http://vis.stanford.edu/protovis/ex/force.html
Again, faster in JM/TM than on m-c but needs more work. See
https://bugzilla.mozilla.org/show_bug.cgi?id=589422 for the gory details, but the upshot is that about half the time here is JavaScript and the other half is other stuff; SVG path performance shows up prominently.
and it goes on
http://acko.net/blog/js1k-demo-the-making-of
That looks about the same to me in Chrome 7 dev and in JM/TM.
No one is saying that there's nothing else to do, of course. But at this point there are also plenty of examples where we're faster than the competition; now all we need to do is be faster on all of them.