Minefield Shows the (Really) Fast Future of Firefox
zootropole writes "If you are using Firefox 3 (or even Chrome) you should consider taking a look at Mozilla's Minefield. This browser (alpha version yet, but stable) would give a new meaning to 'fast browsing experience.' Some Firefox extensions aren't supported, but riding the fastest javascript engine on the planet definitely worth a try. Minefield's install won't affect your Firefox, so there's no risk trying it. It's fast. Really. And I'm loving it."
Reviews popping up around the web are overwhelmingly positive, calling the upcoming browser crazy fast, blisteringly fast, etc.
Are you crazy? If you want to be a little risky, try the 3.1 beta. Nightlies shouldn't be used by those that want to use extensions or avoid crashes.
These are the nightly builds, once they like how the nightly builds work, they will release them as a "Firefox" update.
It has the potential to be, at least for interpreting javascript. The gui still feels a lot more sluggish though, and general rendering still seems quite a bit slower as well. Just remember to do the about:config thing, then search for jit, and turn the two options on to get the speed boost.
Everything will be taken away from you.
Hmmm. It looks like there's still some speed issues that need worked out. Don't worry, I'm sure you'll be able to get first post by Beta 2.
Of course, you have to enable the TraceMonkey JIT JavaScript compiler before you'll see any reasonable speed increase (in theory). Just go to about:config, search for the 2 items with "JIT" in their name, and enable them.
My stress tests have shown it to be 10-50% faster than Chrome *when* JIT works. However, it's still buggy as hell, it eats its own memory heap and grinds to inexplicable halts kinda randomly whenever my code does anything repetitive and strenuous, bringing the average execution speed down to almost FF2 levels, meaning it's faster for me to leave JIT disabled. It's a no-go for me until they fix that.
Today's weirdness is tomorrow's reason why. -- Hunter S. Thompson
People are talking as if Chrome's V8 was the fastest JavaScript engine around, but it wasn't - WebKit's SquirrelFish Extreme was faster. Is Minefield's engine even faster? Ars Technica's tests show that TraceMonkey runs the SunSpider benchmark in between 78% and 84% of V8's time. However, according to earlier tests, SquirelFish Extreme completes the benchmark in 74% of V8's time, making it even faster than the newest TraceMonkey. So it looks like Minefield, though fast, is not the fastest browser in JavaScript.
People. There is A REASON why Mozilla calls these builds "Minefield" rather than "Firefox".
It's because they're not ready for daily use.
They may be faster than the released version of Firefox, but they also may contain major, showstopping bugs, up to and including bugs that can cause data loss.
The only people who should be using them are people who understand this risk and are willing to accept it -- i.e. testers.
Anyone promoting these builds for use by the general public is being irresponsible and exposing anyone who takes their advice to risk.
TFA is bad enough, but it's worse to see major sites like Slashdot parroting this bad advice. You should be telling your friends to avoid Minefield, not to seek it out.
Read my blog.
Seems pretty quick to me, but that's probably cause it's not running my 15+ extensions.
There is a war going on for your mind.
Please remember that if you messed with minefield "a few months back" then its been through dozens of iterations since then. It's a nightly build.
The browser war heated up when Google (and others?) started paying out on ad revenue created by in-browser searches. Apple makes some nice change on Safari. So does the Mozilla Foundation, apparently.
There would be very little competition if there wasn't money to be made.
"DISCLAIMER: Use of this advanced computing technology does not imply an endorsement of Western industrial civilization."
Actually, yes, it does. You're just too much of a hypocrite to recognize it.
-Styopa