Slashdot Mirror


Firefox 8 20% Faster Than Firefox 5

An anonymous reader writes "Thanks to continued improvements to start-up and first paint performance, tweaks to memory footprint and garbage collection, and the addition of a new 2D graphics backend called Azure, Firefox 8 is some 20% faster than Firefox 5 across all major metrics — and actually about equal with Chrome 14 on JavaScript and 2D rendering performance. Azure (which is new with Firefox 7) replaces Cairo, and instead of dealing with Direct2D and Quartz, it allows Firefox to deal directly with the Direct3D and OpenGL subsystems — resulting in a 20% speed boost under Windows, and probably even more under OS X."

27 of 441 comments (clear)

  1. First post by Anonymous Coward · · Score: 5, Funny

    Your post could've been here if you had a faster web browser.

  2. What about Firefox 6? by Anonymous Coward · · Score: 3, Insightful

    I know it's been said before, but this new release system is fucking retarded.

    I'm this close to dumping Firefox on every machine I touch.

    1. Re:What about Firefox 6? by fuzzyfuzzyfungus · · Score: 3, Interesting

      Wait: "This new release system" has resulted in a 20% speedup; but you are this close to dumping it because its version numbering scheme is inaesthetic?

      I agree that the race-to-the-highest-number game is silly; but it is the silly, albeit visible, symptom of the FF team having a fire lit under its collective ass by Chrome. Arguably, while a lot of what gets full numbers really should just be point releases, FF's quality today is relatively better than it has been in some time. Are you really going to let the version numbers get in the way?

    2. Re:What about Firefox 6? by Infiniti2000 · · Score: 5, Funny

      Agreed. I thought I was reading The Onion.

    3. Re:What about Firefox 6? by brian6string · · Score: 5, Funny

      Firefox 8: "The Ocho"

    4. Re:What about Firefox 6? by rudy_wayne · · Score: 5, Funny

      Firefox 8 has a version number that is 100% greater than Firefox 4. Now there's a big improvement for you.

    5. Re:What about Firefox 6? by Tukz · · Score: 4, Insightful

      Tell that to the extentions that constantly break on new major version.

      --
      - Don't do what I do, it's probably not healthy nor safe. -
    6. Re:What about Firefox 6? by compro01 · · Score: 3, Informative

      Addons hosted on addons.mozilla.org are now automatically checked for compatibility with new versions (by checking API calls used by the addon) and are bumped to show as compatible. If not, an email gets sent to the addon developer alerting them to the fact their addon is broken, and what exactly is broken about it.

      This will start happening for the release of 6.

      --
      upon the advice of my lawyer, i have no sig at this time
    7. Re:What about Firefox 6? by VGPowerlord · · Score: 3, Interesting

      Tell that to the extentions that constantly break on new major version.

      Also, tell that to Mozilla's extension approvers, who won't approve any extension marked as having a maxVersion greater than 8, and that was 7 up until a few days ago.

      Granted, you could distribute your Extension through your own site instead of the main Firefox Add-ons site...

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    8. Re:What about Firefox 6? by Errtu76 · · Score: 4, Insightful

      Is it possible to check compatibility of installed extensions before your upgrade? Other than going to the homepage of each extension, that is.

      If not, that would be a nice option:

      "A new version of firefox is available. Checking list of extensions for compatibilty issues ... Done! From 10 installed extensions, the following are incompatible with the new version. Would you still like to upgrade?"

    9. Re:What about Firefox 6? by BitZtream · · Score: 4, Insightful

      It is now. It wasn't once before. At one point, version numbers had meaning, that is until marketing and people such as yourself decided it really didn't matter.

      I've worked doing both support and development and for me, a version number is not 'just a number'. It tells me something about what I can expect.

      The number should be as follows: major.minor.patch.build

      A major version bump means there WILL be compatibility issues. API changes require a major bump. Massive UI/Feature changes warrent a major bump a lot of the time.

      A minor version number means it probably won't break anything unless you have some dependency on a specific bug that has been fixed, which should be unlikely if you followed documented APIs and such. May introduce minor new features, should mostly be features that you missed on the release or where incomplete due to deadlines. Occasionally the 'heh, I forgot that obvious small feature that makes a world of difference' goes here, but for the most part this should be reserved for fixes that may accidently break compatibility.

      A patch version number change means you shouldn't notice any difference other than a security/bug fix.
      The build number is a unique identifier for the developer to reference internally as an exact point in time snapshot of the package. Thats the number that allows the dev to reproduce the exact same build.

      With the exception of a major number change, all other changes shouldn't result in massive breakages, for instance a major version change is the only thing that should break Firefox plugins en masse, and it should be avoided if there is any possible way to do so.

      I want to know what to expect from an upgrade, traditional version numbers help me at a glance determine my risk.

      Firefox (and Chrome) is taking an approach that I could only describe as amateur and completely lacking of any experience of having to support someone elses software product. It indicates you (Mozilla) don't give a flying fuck about what happens to the people who use the browser or what their experience is like, just that they get their way.

      And for the record, going from 4.05 to 4.08 generally would result in my response being something like:

      Great, another Firefox release, wonder how much this one breaks?

      The only people who randomly see a new version of software and get excited for no reason aren't relevant to this conversation. Normal people (the majority of us) have better things to do than worry about the latest release of Firefox. Anyone who does get excited needs to seek counseling.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    10. Re:What about Firefox 6? by hairyfeet · · Score: 3, Insightful

      Not to mention you are losing extremely important information that the classic versioning system gave us, which is why we had it in the first place...when there are gonna be major changes to the code. with the old system if it was a change from .01 to point 02 it was a bug fix, those rarely broke things and if they code was well written a change from .10 to point .20 rarely broke major things although their might be some minor niggles. It was the 1.0 to 2.0 you had to watch out for as THAT is what bit you in the ass.

      Ultimately I think this move is gonna be a major victory....for Chrome The Google juggernaut will make even larger gains thanks to this dickish move and here is why: People tend to use at home what they learn and use at work and no admin with any sense is gonna touch FF now, and most importantly even little guys with not nearly as many people to support as an enterprise are now dumping FF because i don't know when they are gonna break extensions myself and my customers depend on. Finally let us not forget that most extension developers are doing this in their spare time and/or for donations an the crazy release schedule with the 'fuck you, jump on board or piss off" attitude is causing quite a few to spend a LOT less time worrying about the FF extension and instead working on Chrome.

      Lets be honest folks, the extension framework was the only real selling point to FF anymore. Their GUI was becoming more of a Chrome ripoff by the day, in performance tests Chrome and Opera regularly stomped them, all that was left is the extension framework. So what do they do? Take a big old shit on the extension developers!

      This is why I have switched and am switching my users to Comodo Dragon, based on Chromium. So far I have upgraded from Dragon 6 through Dragon 12 without a SINGLE extension breaking, whereas I lost about a third of my extensions going from 4 to 5, including those like the Avast site rating that helped my customers to avoid dodgy sites. The only extension I had on FF I don't have on Dragon is NoScript and as I understand it the Chromium guys are working on an API that will give NoScript the hooks it needs.

      And sorry about the length but as someone who used Firefox before it was even called Firefox, and the Suite before that, this really saddens me. Mozilla has become the rebirth of Netscape, with an arrogant leadership whose code simply can't back up their arrogant attitude. So from me and my customers Mozilla so long and thanks for all the fish.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    11. Re:What about Firefox 6? by toriver · · Score: 3, Insightful

      Because "if our plugins didn't fail to run because Firefox decided to throw version number semantics overboard, they would be running 20% faster" is not a good position to be in.

  3. Firefox 6 is already old-and-busted by MetalliQaZ · · Score: 5, Funny

    Firefox 6 is so out of date, my parents will probably use it when it comes out.

    --
    "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
  4. For those confused by Samantha+Wright · · Score: 5, Informative

    FF8 is the nightly branch, FF7 is the smaller-than-beta branch ("aurora"), and FF6 is the alpha branch. Mozilla hasn't suddenly started to number their versions geometrically, although that would be hilarious.

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    1. Re:For those confused by Abstrackt · · Score: 3, Funny

      this is TARDIS programming

      So wait. Does that mean I get a sonic screwdriver with a new download of Firefox?

      No, it means you get a shower of sparks and your ass dumped in an awkward situation because you hit the wrong button. ;)

      --
      They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance. - Terry Pratchett
    2. Re:For those confused by Schadrach · · Score: 3, Funny

      So, does that mean it has a 5 minute summoning animation??

  5. Wow, talk about version inflation by Fnkmaster · · Score: 5, Insightful

    You fools are only benchmarking Firefox 8!! Well I benchmarked Firefox 14 and it's plus 10 faster than Firefox 4.

    I appreciate the benefits of rapid versioning and release cycles, but really, this is ridiculous.

  6. Ridiculous by Anonymous Coward · · Score: 3, Interesting

    Do you have any idea how it complicates Web contracts? We used to be able to say "your website will be compatible with current version-2 of the browsers" but now that would be ridiculous. We'd never be able to deliver since we would be stuck in a infinite testing loop.

    We'll have to start writing "your website will be compatible with Firefox 5" and by the time we deliver Firefox 12 will be available. I guess we'll have to add a clause about how Microsoft, Google and Firefox are all teenagers who compare their peni- I mean version numbers to feel good about themselves.

    Apple aren't being childish with the whole issue and using sane version numbers. And Opera has been out for quite a long time, though they do seem to be jumping into the version bandwagon as of late.

  7. Firefox 61 by jabberw0k · · Score: 5, Interesting

    By my calculations, if Firefox had started this version numbering scheme with its start in 2004, we would now be running Firefox 61.

    If they Mozilla had adopted it in 1998, this would be Firefox 113.

    Bonkazoids.

  8. Great... yet another version of Firefox to support by leonbev · · Score: 5, Informative

    We just got our web site rendering correctly under Firefox 5, and now there not one but THREE new versions in beta that we also need to test with.

    Just a quick note from the web developers and web site QA testers around the world to the Firefox development team... you're really starting to piss us off.

  9. Re:Firefox 6 & 7? by Millennium · · Score: 4, Informative

    From what I can tell, Mozilla seems to have four versions of Firefox being developed and/or maintained at any given time:

    Current - Whatever is currently released. Only bugfixes usually get ported to this release. Currently FF5.
    Beta - Feature-frozen and reasonably stable, but not quite ready for prime time. Will be the next release. Currently FF6.
    Aurora - Feature-frozen, but not stable. Early QA happens here, though it gets more fleshed out in Beta. Currently FF7.
    Nightly - This is where the new feature development happens. Currently FF8.

    When it's time for release, everything gets promoted: when FF6 is released, FF7 will become Beta, FF8 will become Aurora, and new development will start on FF9.

    I kind of like the idea of putting new code through two entire cycles of public testing. All the same, I do wish that Mozilla would add a Long-Term Support cycle every few versions, akin to Ubuntu's LTS cycle, that people could count on to be supported for more than just a couple of months.

    It is true that sane IT departments upgrade their browsers regularly, but not all IT departments are driven by sanity. This is a sad fact that Mozilla needs to account for, and there's a tested model out there that isn't too dissimilar to Mozilla's own. They should seriously look into adapting the differences.

  10. pfft FireFox 8 by equex · · Score: 4, Funny

    I am already using version 21, its the pre pre pre alpha pre beta pre pre gamma delta pre RC pre build, I'm so bleeding edge I have to buy tampons at the store. My insurance company wont even insure my computer because all my software are practically from the future.

    --
    Can I light a sig ?
  11. Not all addons are on AMO nor in pure JS by tepples · · Score: 4, Insightful
    Anonymous Coward wrote:

    If your addon is on addons.mozilla.org

    Does addons.mozilla.org offer private hosting of bespoke addons used by a single company? Does addons.mozilla.org offer hosting of addons whose use requires payment? Or is addons.mozilla.org intended solely for addons intended for public use at no charge?

    they've begun automatically testing addons for compatibility

    I seem to remember reading that any add-on incorporating a native code component will automatically fail the test.

  12. Re:Rendering by jesser · · Score: 3, Informative

    I'm curious about the change to rendering. It seems to me they're saying, "these OS layout engines (Quartz et al) are too slow - we'll just route around them".

    Precisely the opposite. It's our previous abstraction layer that's too slow, and we're replacing it with a thinner one, starting with the easier things like Canvas. See Introducing the Azure project and Azure vs Cairo.

    --
    The shareholder is always right.
  13. Firefox a cause of Technological Moral Panic by cruff · · Score: 4, Funny

    When I saw "Firefox 8" in the title, I fell into a panic. What happened to 6 and 7? People weren't meant to upgrade their browsers to new major version numbers weekly! No one could possibly survive that pace, their mouse buttons will burn out at the furious pace necessary to install that often! Think of the effect that has on the women and children!

  14. Re:Do not make much sense right now by Anonymous Coward · · Score: 3, Funny

    It'll be alpha on Friday, beta on Sunday, released next wednesday and discontinued next friday.