Slashdot Mirror
Firefox 4's JavaScript Now Faster Than Chrome's
An anonymous reader writes "Firefox 4's JavaScript engine is now faster than V8 (used in Chrome) and Nitro (used in Safari) in the SunSpider benchmark on x86. On Mozilla's test system Nitro completes the benchmark in 369.7 milliseconds, V8 in 356.5 milliseconds, and Firefox 4's TraceMonkey and JaegerMonkey combination in 350.3 milliseconds. Conceivably Tech has a brief rundown of some benchmark figures from their test system obtained with the latest JS preview build of Firefox 4: 'Our AMD Phenom X6-based Dell XPS 7100 PC completed the Sunspider test with the latest Firefox JS (4.0 b8-pre) build in 478.6 ms this morning, while Chrome 8.0.560.0 clocked in at 589.8 ms.' On x86-64 Nitro still has the lead over V8 and TraceMonkey+JaegerMonkey in the SunSpider benchmark."
The moderating of the parent and grandparent comments are excellent examples of why so many people are fleeing Firefox these days. Instead of trying to fix the memory leak problem, any reports are covered up and otherwise swept under the rug by the Firefox community. Anyone pointing out Firefox's excessive memory usage is quickly labeled as a "troll".
The Firefox community has only two options here:
1) Admit that there is a memory leak problem, fix it, and then stand a chance against their competitors.
2) Keep acting like children by sticking their fingers in their ears, closing their eyes, pretending the problems don't exist, and then getting absolutely destroyed by IE, Chrome, Safari and Opera.
Firefox 4 will be the breaking point. If the problems aren't fixed, there probably won't be a Firefox 5 release. Too many people will have fled to the superior alternative browsers.