Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

Minefield Shows the (Really) Fast Future of Firefox

Posted by timothy on Tue Oct 28, 2008 09:20 AM
from the zipping-right-along dept.
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.
technology mozilla itsabrowser firefox fast tech mozilla story

Related Stories

[+] Firefox 3.5RC2 Performance In Windows Vs. Linux 240 comments
pizzutz writes "Andy Lawrence has posted a Javascript speed comparison for the recently released Firefox 3.5RC2 between Linux (Ubuntu 9.04) and Windows(XP SP3) using the SunSpider benchmark test. Firefox 3.5 will include the new Tracemonkey Javascript engine. The Windows build edges out Linux by just under 15%, though the Linux build is still twice as fast as the current 3.0.11 version which ships with Jaunty."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • First Post! (Score:5, Funny)

    by mincognito (839071) on Tuesday October 28 2008, @09:24AM (#25540175)
    thanks to minefield :)
  • by Anonymous Coward on Tuesday October 28 2008, @09:24AM (#25540181)

    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.

    • by ajs (35943) <ajs.ajs@com> on Tuesday October 28 2008, @10:16AM (#25540827) Homepage Journal

      What's more, this is the same thing we hear every 2 years. "Browser X is really fast!" Then six months later you hear, "Browser X was lagging behind the pack because it didn't have support for A, B and C, but now it's getting them." After that you get, "Why is Browser X so slow these days?" And inevitably, "Browser Y is really fast!"

      When are we going to realize that browser maturity and performance are going to be on opposing curves and jumping ship to an immature browser just sets you up to lose functionality for a short period of time until the performance can be gobbled up by it.

      This is exactly why I'm not using Chrome. Chrome is very nice, but it doesn't have most of what I require of a browsing experience. Once it does, THEN I'll evaluate its competitiveness, not before.

        • by meringuoid (568297) on Tuesday October 28 2008, @10:21AM (#25540877)

          Nightlies shouldn't be used by those that want to use extensions or avoid crashes

          I dunno. I use the nightlies at work... I don't use any extensions though.

          +1 Missed the point but still sounded vaguely insightful?

          You missed out the 'or' operator. The original statement was that IF (you want to use extensions OR you want to avoid crashes) THEN you shouldn't use nightlies. The followup said that he used the nightlies and avoided crashes just as well as with the stable release, although he didn't use extensions. So: wants to use extensions FALSE, wants to avoid crashes TRUE, and as it turns out nightlies work just fine. Hence OP's theorem is disproved by counterexample.

          Really, this is basic Boolean logic. Anyone reading /. ought to understand this stuff...

  • Java v. Javascript (Score:5, Insightful)

    by michaelhood (667393) on Tuesday October 28 2008, @09:32AM (#25540295)

    OK, it's time for us to start educating users and the media of when to properly use the monikers Java and JavaScript.

    The article linked to from the summary says "Handles Java Well" in the subtitle, but then never mentions it again - only JavaScript.

    These are NOT THE SAME.

    This is, of course, CBSNews.. but I have seen the same mistake in so-called "tech" media lately, too.

  • by $RANDOMLUSER (804576) on Tuesday October 28 2008, @09:33AM (#25540313)
    Another browser to test on!!!

    "Hey Rockie, watch me put a gun in my mouth!"
  • by jalefkowit (101585) <jason@@@jasonlefkowitz...net> on Tuesday October 28 2008, @09:52AM (#25540545) Homepage

    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.

    • by SkankinMonkey (528381) on Tuesday October 28 2008, @09:56AM (#25540609)
      I don't think anyone is encouraging the masses to use a nightly. However, slashdot is "News For Nerds" right? Nerds should be able to use a nightly without destroying their computers beyond recognition, if not they need to give their badges back.
      • by jalefkowit (101585) <jason@@@jasonlefkowitz...net> on Tuesday October 28 2008, @10:11AM (#25540779) Homepage

        You got lucky.

        A nightly build is exactly what it says it is -- a snapshot of the codebase as of a given day.

        Some nightly builds may be completely bug free. Others may be chock full of major dataloss bugs. It's a crapshoot.

        Your friends may be fine today, but if they decide to "update Minefield" on the wrong day in the future, they're gonna get screwed.

        That's why I call it irresponsible.

  • No thanks (Score:5, Insightful)

    by andy1307 (656570) on Tuesday October 28 2008, @10:13AM (#25540803)
    The biggest advantage of firefox is the ability to block out javascript via NoScript. Why would I want to give that up?
    • by Joe Tie. (567096) on Tuesday October 28 2008, @09:32AM (#25540289)
      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.
    • by LSD-OBS (183415) on Tuesday October 28 2008, @09:45AM (#25540457)

      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.

    • by Shin-LaC (1333529) on Tuesday October 28 2008, @09:45AM (#25540461)
      People are talking as if Chrome's V8 was the fastest JavaScript engine around, but it wasn't - WebKit's SquirrelFish Extreme was faster [slashdot.org]. Is Minefield's engine even faster? Ars Technica's tests [arstechnica.com] show that TraceMonkey runs the SunSpider benchmark in between 78% and 84% of V8's time. However, according to earlier tests [blogspot.com], 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.
      • by tnk1 (899206) on Tuesday October 28 2008, @10:24AM (#25540911)

        My ManBearPig smashes your SquirrelFish and your silly TraceMonkey.

        Since I am not going to RTFA, I am going to speculate that Minefield is Mozilla's answer to Microsoft by way of having a faster, more modern version of Minesweeper.

        Take that Evil Empire!

    • Re:Minefield? (Score:5, Informative)

      by michaelhood (667393) on Tuesday October 28 2008, @09:38AM (#25540373)

      What the hell kind of codename is that? Maybe an attempt at 'truth in advertising'?

      That's exactly what it is. Minefield always refers to the current alpha-release of the upcoming "major" release.

      Don't use it unless you know what you're doing. Suggesting end-users use this, without briefing them on why it will crash [frequently], is irresponsible at best and does a disservice to the alternate browser movement.

    • by Mr Z (6791) on Tuesday October 28 2008, @10:02AM (#25540683) Homepage Journal

      Well... it's 10% faster than Chrome, not than Firefox 3. So, to use your analogy, it's like you're going down the road at 35MPH when Chrome blows by doing 80, and then Minefield blows past doing 88MPH.

      (Just better watch that flux capacitor...)

    • by Ash-Fox (726320) on Tuesday October 28 2008, @10:14AM (#25540811) Homepage

      All these years people in the Unixy world gave Microsoft a ton of crap for VB, and now, after all this time, they've come up with something arguably worse... javascript, and now, a javascript compiler.

      Javascript was not created by the opensource community (it was created by Brendan Eich and ended up becoming part of Netscape, which was not open source at the time). Additionally, Javascript has reasonable structures that don't deteriorate when the software expands to large sizes.

      Check out Synchronet [synchro.net], it has IRC servers, NNTP servers, Gopher servers etc. all written in javascript. The code is completely readable (generally not the case with VB when the code reaches that complexity) and cross-platform.

      There is nothing fundamentally wrong with the Javascript language, like there is in visual basic.

    • by hraefn (627340) on Tuesday October 28 2008, @10:31AM (#25541009) Homepage

      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 [clickz.com].

      There would be very little competition if there wasn't money to be made.