Slashdot Mirror


Firefox 4 Will Be One Generation Ahead

An anonymous reader writes "Mozilla's Chris Blizzard talks about the rising competition by Google Chrome, the evolution of the web platform and the prospects for WebM. He also promises that Firefox 4 will be 'one generation ahead' of other browsers in relation to Javascript speed."

12 of 341 comments (clear)

  1. ...And one generation behind on HTML5 by elrous0 · · Score: 5, Insightful

    Look, I *love* Firefox. I use it pretty much exclusively myself. Nothing can touch add-ons like NoScript, AdBlock, etc. (and most of my add-ons and their associated functionality can't be found on Chrome, Opera, etc.). But if they think that Google, who provides about 85% of Mozilla's total revenue, is going to sit back and let them take the technical lead over Chrome, they're nuts. And speed has always been one of Chrome's few positive qualities over Firefox.

    Not only that, but Mozilla can't afford to license h264. And that already puts them behind on HTML5. I am hoping that either html5 never catches on, the other browsers all agree to an open format (like WebM), or there is some kind of flash-player type add-on made for Firefox to support h264. But without one of those, Firefox is (sadly) already in a rough spot for the next gen.

    And I say all that as someone who hates the idea of giving up my Firefox and having to get my browser from an increasingly-evil Google, an already evil Microsoft, or a closed-off Opera. If I wanted evil and closed, I would have bought an iPad, not a netbook.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
    1. Re:...And one generation behind on HTML5 by Ethanol-fueled · · Score: 5, Insightful
      From the summary:

      He also promises that Firefox 4 will be "one generation ahead" of other browsers in relation to Javascript speed."

      The browser vendors' fetishistic obsession with Javascript speed is most irritating.

    2. Re:...And one generation behind on HTML5 by betterunixthanunix · · Score: 5, Insightful

      if they think that Google, who provides about 85% of Mozilla's total revenue, is going to sit back and let them take the technical lead over Chrome, they're nuts.

      Except that Google benefits from faster Javascript engines in any browser, not just Chrome. Firefox is a popular browser, and if Firefox can execute Javascript faster, that means that Google's web apps (which I am just going to guess account for more revenue than Chrome) will perform better. It also means that Google could potentially do more, i.e. have heavier Javascript programs, without worrying that people are going to get annoyed at how slow their applications are. How does Google lose here?

      --
      Palm trees and 8
    3. Re:...And one generation behind on HTML5 by garcia · · Score: 5, Informative

      The browser vendors' fetishistic obsession with Javascript speed is most irritating.

      I have mod points but I decided to respond instead... I agree with you, it is irritating especially when the browser's speeds themselves are miserable. Yay great, Chrome loads faster but I have random issues with plugins which affect my work (one of the plugins is disabling me from reading GMail messages) and AdBlock still doesn't work nearly as well as it does on Firefox for the sites I use most often.

      I wish Firefox would stop trying to compete in Javascript and go back to one of the biggest reasons they started the project: speed of the browser itself. That means it should open instantaneously and have low overhead--even with the usual plugins installed (AdBlock, NoScript, etc).

    4. Re:...And one generation behind on HTML5 by Haedrian · · Score: 5, Insightful

      That's because most 'web applications' (such as google docs) or stuff like Facebook is chock full of Javascript.

      In ye olde days when java script was just used to pull up a popup or block your right clicks it wasn't so important, but nowadays most popular sites are full of it. Whenever you need 'dynamic' content on a web page - that's Javascript.

      Even /. by the way.

    5. Re:...And one generation behind on HTML5 by maxwell+demon · · Score: 5, Insightful

      Don't the extensions (at least the cross-platform ones) implement their functionality mostly in JavaScript? If so, then improving JavaScript speed would do very much to fulfil your wish.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    6. Re:...And one generation behind on HTML5 by Anonymous Coward · · Score: 5, Insightful

      Show me where h264 is a requirement in the HTML5 spec.

      kthx.

      Show me where GIF, PNG, JPG, BMP and ICO are required for the IMG tag in the HTML 1/2/3/4/5 spec.

      Now tell me what you'd think about browsing without support for these in anything, but lynx.

      kthx.

    7. Re:...And one generation behind on HTML5 by TeXMaster · · Score: 5, Insightful

      Exactly. The main problem I have with Firefox is that by the time I've customized it to my liking, it's unusably slow.

      Maybe you should consider a browser that doesn't need to be bogged down to death to be useable. One of the reasons why I use Opera, for example, it's precisely that it does all the stuff I want it to do without me needing to scrape around the web to get extensions that kill it.

      --
      "I'm never quite so stupid as when I'm being smart" (Linus van Pelt)
    8. Re:...And one generation behind on HTML5 by marsu_k · · Score: 5, Informative

      Regarding the "awesome bar" (I really like the functionality, but loathe the name), the sqlite database can get fragmented over time. You might want to try this ever now and then. Can make a world of difference, especially with slower computers/disks.

    9. Re:...And one generation behind on HTML5 by morgan_greywolf · · Score: 5, Insightful

      Yep. JavaScript :: Firefox as Lisp :: Emacs

  2. Re:SQLite database vacuum by Sami+Lehtinen · · Score: 5, Informative

    There are a few alternatives to yet another plugin:
    1) You can use standalone SQLite3 installation to open bases and vacuum those.
    2) Use Python script for vacuuming.
    3) You can use Error Console with following string to vacuum bases:
    Components.classes["@mozilla.org/browser/nav-history-service;1"].getService(Components.interfaces.nsPIPlacesDatabase).DBConnection.executeSimpleSQL("VACUUM");
    I personally prefer last option, beacuse no additional software is required.

  3. Re:SQLite database vacuum by jameson71 · · Score: 5, Insightful

    Yeah, but it would be nice if a *web browser* didn't require DBA level maintenance to keep it working right.