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."

3 of 341 comments (clear)

  1. Re:...And one generation behind on HTML5 by chomsky68 · · Score: 0, Redundant

    exactly my sentiments!

    --
    I'm Not Antisocial, I'm Just Not User Friendly
  2. javascript speed? by hobo+sapiens · · Score: 0, Redundant

    These guys are starting to sound like MSFT when they released IE7.

    What's with the fight over javascript speed? It's as ludicruous as MSFT touting tabbed browsing on an aging and stodgy codebase. People aren't leaving for Chrome en masse due to javascript speed. How about making the browser move faster and use less memory? So long as I don't have to WAIT an appreciable length of time for javascript to run, I don't care if it takes 3 milliseconds or 3 picoseconds.

    What do my old-as-dirt dell latitude running XP, my old dell running xubuntu, and my shiny new macbook have in common? Firefox is the slowest browser of Chrome, Safari, IE, and Opera in terms of opening up, opening tabs, rendering pages. In other words, Firefox is still the slowest browser in most things that matter and save for safari on the Mac, uses the most memory.

    I hate to see this happen to firefox. It's like watching and old friend slowly grow insane.

    --
    blah blah blah
  3. Re:...And one generation behind on HTML5 by marsu_k · · Score: 0, Redundant

    Don't quote me on this - I can't be arsed to google it, and might remember wrong - but I seem to recall a discussion that this feature (automatic vacuuming of the databases, when they're either fragmented over a certain threshold, or when the last vacuuming was n days ago) was to be implemented into a next version of FF, 3.5? 3.6? Can't remember. From what I can tell, it still hasn't been implemented. Yes, it definitely should be built-in.