Mozilla Rechallenges Google in Browser Speed Race
The browser speed war appeared to be pretty much over, until a few days ago, when Mozilla's JIT compiler lead David Mandelin sent out a tweet that the new JIT IonMonkey has eclipsed Chrome in at least one configuration on Mozilla's Kraken benchmark.
Posted on Mozilla's AreWeFastYet page - which was originally established when Mozilla began working on JaegerMonkey (that arrived with Firefox 4 and is still in use today) - Firefox 17 with IonMonkey squeezes the win with a performance of 1991 ms versus Chrome's 2038 ms. Mandelin notes that this result is achieved on a Mac Pro with a 32-bit version of the browser.
Of course, JavaScript benchmarks were interesting two years ago and it seems we have largely lost interest in the millisecond race, but I was nevertheless interested in those claims. In the end, Mozilla promised in 2009 that it would try to catch up with Chrome and if it can do it now, even if it is a bit late, it's noteworthy since it kept its promise.
I was not able to replicate the claim on my venerable Phenom II X6 Windows 7 system. Chrome won with 3349 ms versus 3715 ms for Firefox. However, IonMonkey gained almost 20 percent of speed over the current JaegerMonkey in Firefox 15 beta, which came in at 4627 ms. Perhaps there is still some room left for faster JavaScript engines?

Nevertheless, it would be nice of Mozilla to iron out any bugs. That includes you, Adobe.
I become somewhat worried if a problem also existed in version 15 and maybe even 14.
And for your information, I gave Beta a try. The problem also exists.
It is not official. Thus not made by Mozilla.
Except it is official. Mozilla formally added it as one of their own projects. It may have started out as an unofficial branch, but Mozilla owns it now. Therefore, it is being made and maintained by Mozilla.
It is frustrating to look at a webpage, even a fairly basic one, in 3 different browsers and see it rendered differently; then having to explain the difference to the client :-(
Then, someone on the client side has the bright idea of pointing out that it's broken in IE8, IE7, and especially IE6.
For some reason, it keeps giving me "Luna error" and AVG is marking it as a virus...
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central-l10n/
Also with the exception of silverlight every other plug-in works fine out of the box for the 64-bit version. Silverlight requires a little more effort to get it working properly.
If you pull down the bar on the top of that page you will see this message.
http://www.palemoon.org
if you, like me, dont like the UI changes mozilla have done, then Palemoon is for you. It retains the FF4 UI, with full customisations possible. The browser is built with full profile guided optimisation. It also contains patches from the beta channels, that cant come in firefox due to hierqrchial and corporate policies. It has a 64 bit version too.