Slashdot Mirror


Firefox 8.0 Released

Today Mozilla announced the launch of Firefox 8.0. The headline features this time around include adding Twitter as a search bar option, tab loading tweaks, and the default disabling of addons installed by third-parties. "Sometimes you download third-party software and are surprised to discover that an add-on has also installed itself in your browser without asking permission. At Mozilla, we think you should be in control, so we are disabling add-ons installed by third parties without your permission and letting you pick the ones you want to keep." Here are the release notes and download links.

12 of 383 comments (clear)

  1. You mean... by jellomizer · · Score: 4, Interesting

    Firefox 4.04

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:You mean... by Grishnakh · · Score: 4, Insightful

      I have no idea why Mozilla thought doing the Chrome name scheme was a good idea. I have no idea why Chrome thinks it is a good idea.

      Chrome doesn't think it's a good idea, which is why Chrome doesn't do it. Try this: find a bunch of Chrome users, and ask them which version of Chrome they're using. Most of them probably won't know. That's because Chrome doesn't advertise its release numbers, they just push everyone to use the latest. It's only Firefox that's running around screaming about their version numbers.

      All it does is make every release irrelevant and makes it so you can't hype new tech in the browser because to every user it is just "oh, another version".

      Releases should be irrelevant for a stable product; users should just be downloading the updates and using them when offered so they have all the latest security fixes, but there's nothing to get excited about. I don't see Google screaming about every new Chrome release that comes out. If there's a big change in the tech somewhere, they might trumpet that, but they don't make a new version that's not obviously different from the previous version, then make some giant new press event out of it.

    2. Re:You mean... by BZ · · Score: 5, Informative

      > It's only Firefox that's running around screaming
      > about their version numbers.

      Screaming where? http://www.mozilla.org/en-US/firefox/fx/ doesn't say what version you're downloading. Updating from Firefox 7.0.1 to Firefox 8 never says anything about Firefox 8; the experience is exactly the same as the update from 7.0.0 to 7.0.1.

      > I don't see Google screaming about every new
      > Chrome release that comes out.

      It does it just as much as Mozilla does. Compare http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html and http://blog.mozilla.com/blog/2011/11/08/mozilla-firefox-adds-twitter-search-and-new-features-that-make-web-browsing-easier/ which are both the official announcements for Chrome 15 and Firefox 8 as far as I can tell.

      What exactly makes the latter "screaming" while the former is not?

  2. Don't bother by DesScorp · · Score: 5, Funny

    Firefox 9.0 will be out next week.

    --
    Life is hard, and the world is cruel
  3. Re:Negative comments by MobyDisk · · Score: 5, Insightful

    The sanity of the Firefox team is under question as of late. From what I can remember:

    * Incrementing the major version number with every slight tweak is annoying.
    * Worse yet, the reasoning behind it is stupid. They just want their version number to be big, like IE.
    * Major feature creep: they keep talking about the browser as an OS, and 3D acceleration, and stuff that has no purpose in a browser.
    * The long-standing issues about Firefox are being ignored: primarily memory and performance.

  4. best FF upgrade yet by Tumbleweed · · Score: 5, Informative

    Completely smooth upgrade, no incompatible plugins, and lazy tab loading is the best feature ever for tab-crazy people like myself. Since they got the memory use under control in v7, life is good. With Chrome taking up 2-3x more memory than FF, I just can't deal with that anymore. Plus lazy tab loading is now my killer browser feature. Gotta have it. I think FF9 (Dec 20) or FF10 is supposed to have even more substantial memory reduction applied.

  5. Re:slow down cowboy! by MachDelta · · Score: 4, Insightful

    Try it anyways.
    I just upgraded and all of my plugins are working just fine.

    Firefox's biggest problem isn't anything technical - it's that once they DO fix an outstanding issue, no one seems to recognize it. And IMO it would be a crying shame to kill a competent browser because of bad PR.

  6. Re:Negative comments by kripkenstein · · Score: 4, Informative
    Hi there, I'm a developer at Mozilla. Some responses to your comments:

    The sanity of the Firefox team is under question as of late. From what I can remember:

    * Incrementing the major version number with every slight tweak is annoying.

    I understand that this annoys some people. But both Chrome and Firefox do it now, and benefits and detriments are well known. It's not a perfect approach, but it does have its advantages. I don't think both Google and Mozilla are 'insane' ;)

    * Worse yet, the reasoning behind it is stupid. They just want their version number to be big, like IE.

    The main reason for Chrome and Firefox doing this is to get improvements faster to users. Rapid releases allow that.

    Mozilla also has the reason that it is following Google's lead. Google started with this version numbering scheme, and not inventing a new one is better for everyone - less confusion.

    * Major feature creep: they keep talking about the browser as an OS, and 3D acceleration, and stuff that has no purpose in a browser.

    That is a long discussion, for sure! But this is nothing to do with Firefox. All browsers are including 3D acceleration (well, except for IE) and other OS-like features. Google is even pushing native code in the browser (which I think is taking things too far).

    * The long-standing issues about Firefox are being ignored: primarily memory and performance.

    We are working very hard on those issues. If you try this release, I think you'll see significant improvements on both issues, and there are even more in the pipeline for the versions coming up afterwards.

  7. Re:Heck, I'll one up that by Chris+Burke · · Score: 4, Funny

    Hey that's good to hear. Do you also have a plugin for plugging your plugin? And if you used the plugin-plugging plugin to plug your plugin-plugger, would the internet stack overflow? :)

    --

    The enemies of Democracy are
  8. Re:To bad it isn't 3.x by smellotron · · Score: 4, Insightful

    Do you think you'll still be using Firefox 3.6 in 10 years?

    No.

    If not, then what's stopping you from upgrading now?

    The tendency of the developers to mess with the UI means that I expect to weigh the value-add of the new features against learning whatever has changed in the new release. If nothing is bothering me now about the previous release, then I don't want to bother with this calculation. I have more important things to do with my life, like post on /. on threads bitching about web browsers.

    Would it be easier to adapt going from XP to Vista to Win7 to Win8, or from XP straight to Win8?

    I skipped Vista and had no problems with Win7. Back in the day, I wish I had skipped ME. I also skip non-LTS Ubuntu releases. Frankly, I hate OS upgrades on my personal machines.

    "I refuse to adapt to change"

    You're painting with broad, inaccurate, and needlessly offensive brush strokes there, buddy. Software exists to Get Shit Done, so change is not intrinsically good. If a new version of my web browser helps me to Get More Shit Done Faster, then I'll download it immediately. If a new version of my web browser instead destabilizes a tiny part of my life without improving my Get Shit Done Benchmark, then why should I adopt it at all?

  9. Plugins are tied to version in FF, but not Chrome by bigtrike · · Score: 4, Insightful

    From what I can tell, your plugin interface is still using version number to determine plugin compatibility, causing plugin authors to do a lot of extra work. The plugin interface should be frozen and versioned and changed infrequently, so plugins could go more than a month without updates. Yes, Chrome updates frequently, but it never disables half of my plugins on update every month and declares that they don't work like firefox did before I ditched it.

    Why not stabilize the plugin interface for some long time period (more than a month) and version it?

  10. Re:Negative comments by Tom · · Score: 4, Insightful

    Mozilla also has the reason that it is following Google's lead. Google started with this version numbering scheme, and not inventing a new one is better for everyone - less confusion.

    What was wrong with the old one? You know, major and minor numbers, increase the major number only on significant, major changes? Add a third number for bugfixes and cosmetic updates?

    They've thrown out a perfectly good numbering scheme because some dofus in marketing has read a psychology book too many and convinced himself that "bigger == better" will convince the minds of more consumers.

    I understand that this annoys some people.

    No, you don't. This doesn't annoy people, it actively pushes them to change the default browser that they've been using for a decade. You are losing your most loyal users. I hope you remembered to list that under "detriments", and you have something more valuable under "benefits", though I can't imagine what that would be.

    As little as a year ago, I'd be telling anyone who uses anything else that I'd recommend Firefox. Today, I shut up unless they use IE, in which case I tell them to use any other browser of their choice.

    --
    Assorted stuff I do sometimes: Lemuria.org