Slashdot Mirror


Mozilla Firefox 6 Released Ahead of Schedule

BogenDorpher writes "Mozilla is currently on schedule to release Firefox 6 on August 16th but it looks like the final version has already been signed off and is unofficially available on Mozilla's servers."

415 comments

  1. too late by Anonymous Coward · · Score: 0, Troll

    Chrome it is. Webkit is the future.

    Sorry Mozilla, but you missed the train.

    1. Re:too late by creat3d · · Score: 1

      Speak for yourself.

      --
      Grammar nazis are to this community what excrements are to gold.
    2. Re:too late by Samantha+Wright · · Score: 3, Interesting

      When Chrome finally fixes text-shadow rendering on Windows and doesn't act like a lazy dog when you set background-size: cover on a fixed background image, let me know. On that day, you just might be right.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    3. Re:too late by gmuslera · · Score: 1

      Too late? Something else is in the future? Missing the train?

      You can't please everyone, you release early and thats what you get.

    4. Re:too late by deains · · Score: 1

      When Chrome finally lets you use a sidebar, perhaps. Right now I'm sticking with Firefox - I like to be able to actually find things in my bookmarks menu, thanks.

    5. Re:too late by derGoldstein · · Score: 1

      On Chrome it's Ctrl+Shift+O -- Bookmark manager.
      I prefer Firefox's separate window approach, and it does give you better sorting options, but it's not entirely fair to say that it's not possible to find things in the bookmarks menu in Chrome.

      --
      Entomologically speaking, the spider is not a bug, it's a feature.
    6. Re:too late by Beelzebud · · Score: 2

      3 cheers for the good old days of browser monopolies!

    7. Re:too late by semi-extrinsic · · Score: 1

      Try again when Chrome finally has a useable Vim mode. Pentadactyl for Firefox rocks hard, while Vimium is just useless.

      --
      for i in `facebook friends "=bday" 2>/dev/null | cut -d " " -f 3-`; do facebook wallpost $i "Happy birthday!"; done
    8. Re:too late by znrt · · Score: 0

      Speak for yourself.

      It's pretty obvious that Chrome scared the shit out of Mozilla. Being for years the only remarcable contender (hats off) for ubicuous IE crap, from 3.0 on FF just got fatter and fatter. At 3.5 I even swiched to Opera because of FF being so overloaded and bulky wtih useless dumb eye candy that slowed everything down. Then those evil guys at google suddenly come up with some REAL new ideas and improvements... They shook the whole browser bizz (just look how IE, FF, Opera just rushed to copy chrome's ideas), but that's clearly the end of FF's leading role in particular. This dumb release flopping is just hysterical need for hype. But so long. Sure, it's still a good browser, and there's the extensibility thing for which I will still keep FF around for specific tasks ... but in terms of user share FF is doomed. Yes, by Chrome. And future is still painted IE-deep-retard-blue, nerds will use whatever they find cool (insignifficant in the large picture) and the smart option will be ... yep, Chrome, for a while. (Until it becomes fatassed and fucked, just like FF).

    9. Re:too late by improfane · · Score: 1

      Welcome back zget.

      You might have to create another account now.

      --
      Slashdot needs Geekcode | Can anyone recommend any good SCIFI? My tastes: Foundation, Startide Rising, CITY, Ringworld,
    10. Re:too late by Anonymous Coward · · Score: 0

      Something you tech folk here at Slashdot often forget is the majority of the world doesn't give a shit whether their browser has a useable VIM mode.

      As long as it's fast, which Firefox WASN'T, for a VERY, VERY long time.

    11. Re:too late by errandum · · Score: 1

      No, the perceived bloat is, believe it or not, the addons people use.

      The biggest difference between them and chrome is that chrome first loads the UI and lets you see "something" before they go and load their addons (they even seem to start loading the home page - if you have one - before every addon is there). This is not real speed, but actually perceived speed - which is actually a web-1-0-1 rule. You don't need to be faster, you just need to look faster and/or busy when you're not.

      Firefox actually finishes loading everything before they go ahead and render something. This might look good on paper, but it isn't. Those 2 seconds of "nothing" are noticed and usually enough for someone else to get bored and click some other browser.

    12. Re:too late by yourdeadin · · Score: 0

      I second that

    13. Re:too late by creat3d · · Score: 1

      Bloat? What bloat? If you've got a hundred add-ons maybe that's the case, FF loads very quickly for me and runs without a hitch. And if "user share" meant anything, that would mean IE6 was a valid choice.

      --
      Grammar nazis are to this community what excrements are to gold.
    14. Re:too late by Anonymous Coward · · Score: 0

      You're confusing what matters to a developer/designer/savvy user with what matters to a regular user. Don't forget the average user was more than happy with the train wreck that was IE6 for many years.

    15. Re:too late by SenseiLeNoir · · Score: 1

      I fully agree with you...... and I myslef DO use firefox more than chrome..... Partly because I was a Mozilla volunteer back in the day.

      BUT.. lets look at the bigger picture....

      Isnt it great that today we have a CHOICE between great broswers (and even IE is not as sucky any more)? Today we can choose a browser based on OUR personal requirements, rather than half assed support by one or two browsers? Where we no longer have to LIVE with "this site is best on x?"

      I joined Mozilla because of the lack of choice. I wanted an even playing field with a lot of different browsers, that largely display web pages based on standards. The choice is then based on pure user preference.

      Back in 1998, the choice was just IE, or Netscape 4. That was like choosing betweeen death by electricution, or gas chamber!

      --
      Have a nice day!
    16. Re:too late by DrXym · · Score: 1

      Assuming what you say to be correct, that probably is in no small part because of the flexibility that Firefox addons enjoy. They can literally change the user interface, replacing buttons, adding stuff, so they must be installed and running before the app can do anything else. I think Mozilla are aware of the problems that bad add ons can cause which is why they've been spanking them so hard, naming & shaming the worst of them. FF6 for example doesn't allow addons to be installed by stealth (e.g. by Skype) presumably because they can really destabilize the product and FF would get the blame.

  2. Exe may be there, so? by Anonymous Coward · · Score: 4, Informative
    The index.html in each directory still says

    Thanks for your interest in Firefox 6 We aren't quite finished qualifying Firefox 6 yet. You should check out the latest Beta. When we're all done with Firefox 6 it will show up on Firefox.com.

    1. Re:Exe may be there, so? by asto21 · · Score: 2

      I just downloaded and tried it out. The tab that auto loads when you first run a new version of Firefox is titled "Welcome to Firefox Beta" and the page itself says "You are now running Firefox Beta"

    2. Re:Exe may be there, so? by asto21 · · Score: 1

      I went to Help->About Firefox and release version is 6.0. It says "You are currently on the release update channel" and not beta update channel. This is just confusing now.

    3. Re:Exe may be there, so? by BenoitRen · · Score: 2

      They're still mirroring the release. It's not the first time that some idiot submits a story like this.

    4. Re:Exe may be there, so? by pep939 · · Score: 1

      I second that... makes you wonder how this is news for "nerds" sometimes...

    5. Re:Exe may be there, so? by Samantha+Wright · · Score: 2

      They probably just haven't gussied up the page for the release version yet. If you're feeling gutsy, though, why not take up Nightly? The current builds are very stable and have better memory management than 6 will probably provide.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    6. Re:Exe may be there, so? by houghi · · Score: 1

      This is because the people responsible for the version numbering can't keep up. I understand. They need to sleep sometime and before you know it 17 newer versions were released.

      --
      Don't fight for your country, if your country does not fight for you.
    7. Re:Exe may be there, so? by starofale · · Score: 2

      I wouldn't recommend Nightly for normal browsing. You'd be better off with Aurora (Firefox 7) if you want the new features sooner but also like to be sure Firefox will start after every update.

    8. Re:Exe may be there, so? by asto21 · · Score: 1

      Wow! I'm trying out Firefox 8.0a1 right now and it's got a much smaller memory footprint than Firefox 5. I hope it stays that way till tomorrow morning!

    9. Re:Exe may be there, so? by Samantha+Wright · · Score: 1

      In general, I'd agree with you—I've been burned on bad nightlies on a few occasions in the past—but truth be told, they've been smooth sailing since FF4 came out. Either the devs are getting more careful, or less ambitious. *shrug*

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    10. Re:Exe may be there, so? by RebelWebmaster · · Score: 1

      Mozilla has a pretty extensive automated test infrastructure that runs on every checkin. Also, the major work is done on different project branches and made stable before landing on mozilla-central (the mainline Nightly branch), hence the better stability of the Nightly builds.

    11. Re:Exe may be there, so? by ifiwereasculptor · · Score: 1

      I'd guess the shorter release cycle is organizing their ambitions. Instead of implementing twenty new features and then refining them for months, now they add one or two features and immediately hone them for release. So less things are broken and remain so for a shorter period of time.

    12. Re:Exe may be there, so? by Samantha+Wright · · Score: 1

      Yep. And when they're ready to implement their fully automatic update system, no one will even care or worry about what version they've got. So, really, the score's in favour of the shorter release cycle.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    13. Re:Exe may be there, so? by AmiMoJo · · Score: 1

      Here's a better idea: port your favourite extensions to Chrome.

      That's what I'm doing. Easier than forking Firefox and better than my current solution of running 6 add-ons and an array of userChrome/userContent/about:config/UI hacks to keep it usable. Chrome is the new fast and minimal browser, Firefox became Netscape Navigator again.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    14. Re:Exe may be there, so? by Samantha+Wright · · Score: 1

      Chrome's developmental process is too minimal. There are two visual performance bugs in particular that really get under my skin (awful text-shadow rendering on Windows and inefficient display of background-size: cover) that make me want to kill small animals when I run into them. Since I don't have a graphics background (or enough systems engineering experience to delve into an application as complex as a web browser) all I can do is stand in the bug tracker and stamp my feet. Some of my favourite extensions are supported on Chrome, but at the end of the day, as a web designer, I've decided that I'd rather use a browser that respects my choice of Windows visual style on XP.

      The list of reasons I feel unnerved around Chrome is surprisingly long, and surprisingly doesn't feature any of the old privacy complaints. Extensions ain't enough.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    15. Re:Exe may be there, so? by Grishnakh · · Score: 1

      Some of my favourite extensions are supported on Chrome, but at the end of the day, as a web designer, I've decided that I'd rather use a browser that respects my choice of Windows visual style on XP.

      I am a biologist. Please ask me your questions. I will phrase answers as car and computer analogies if possible.

      Which is it?

    16. Re:Exe may be there, so? by Samantha+Wright · · Score: 1

      It's both. And more. But saying you're a polymath in public sounds insufferably arrogant. So I don't. I spent half of this summer recoding the website for a research lab, if it helps convince you at all.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  3. Why not just wait for version 7? by EmagGeek · · Score: 5, Funny

    After all, it'll be out Friday..

    1. Re:Why not just wait for version 7? by Rizimar · · Score: 1

      I almost downloaded it, but between reading your post and checking the page, it's now up to version 11.

    2. Re:Why not just wait for version 7? by MightyMartian · · Score: 1

      This message brought to you by Anonymous Troll version 238

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    3. Re:Why not just wait for version 7? by madprof · · Score: 1

      No, it's 13 now. Do keep up!

    4. Re:Why not just wait for version 7? by eugene2k · · Score: 1

      Mozilla still has a lot of catching up to do before Firefox can reaches Chrome's maturity level. After all everyone knows that the version number reflects the quality of the code and the features offered by the product.

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    5. Re:Why not just wait for version 7? by 346984 · · Score: 1

      Damnit!! I'm only running Anonymous Troll version 236

    6. Re:Why not just wait for version 7? by Kanasta · · Score: 4, Informative

      So now I only have 2 plugins left not supported by FF4, should I upgrade to FF6? My bank also keeps saying FF4 is unsupported (only supports IE6+ and NS and FF3). Hmm, at this rate FF is going to lose users.

    7. Re:Why not just wait for version 7? by MightyMartian · · Score: 1

      Pah! That's at least fifteen minutes old. Christ man, we're already up to AC version 255, 256 by the time I finish this sentence.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    8. Re:Why not just wait for version 7? by dutchwhizzman · · Score: 2

      Maybe it's your bank that should be losing users. If they don't keep up with browser developments, they most likely will be lacking in their security developments as well? Myself I'd expect chrome, safari and the (almost) latest firefox on the list of supported browsers of any bank that I would take seriously.

      --
      I was promised a flying car. Where is my flying car?
    9. Re:Why not just wait for version 7? by Anonymous Coward · · Score: 0

      For me it would be a lot easier to switch browsers, even for just that one site, than switch banks.

    10. Re:Why not just wait for version 7? by Bill_the_Engineer · · Score: 1

      Maybe it's your bank that should be losing users. If they don't keep up with browser developments, they most likely will be lacking in their security developments as well? Myself I'd expect chrome, safari and the (almost) latest firefox on the list of supported browsers of any bank that I would take seriously.

      Why blame the bank? I only consider browsers that manage their updates responsibly and place standards compatibility above eye candy. Not saying I mind UI improvements. As long as the UI improvements don't break compatibility with websites or add ons that gave the browser an edge over the other browsers in the first place.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    11. Re:Why not just wait for version 7? by EdgeCreeper · · Score: 1

      For you there is User Agent Switcher.

    12. Re:Why not just wait for version 7? by EmagGeek · · Score: 1

      Must be the commemorative Spinal Tap version!

    13. Re:Why not just wait for version 7? by Anonymous Coward · · Score: 0

      Maybe it's your bank that should be losing users.

      I wish it worked that way.

    14. Re:Why not just wait for version 7? by PybusJ · · Score: 3, Interesting

      Changing banks is quite a lot hard than changing browser. I know from experience several years ago of changing my bank for not supporting anything other than IE6.

      On the other hand, I do expect my bank to be fairly conservative in the rate at which it makes site changes (unless to patch a security issue); I understand that testing, validation and sign-off of new versions takes quite a while in a large organisation and I realise that operations people may want to schedule upgrade to a new version of the site for a particular time with some notice.

      I don't work in finance, but I do deliver web-based systems, and have been wondering what to do about the rise of Chrome and its frequent silent upgrades. My strategy on projects has been to promise support for the most important IEs (soon, I hope, that won't include IE6), the last couple of major Firefoxen, and current Safari. Chrome is on a best efforts, should work but no guarantees, basis which has worked while it had fairly small share.

      Now that Firefox moves its update regime in the same direction as Chrome (incidentally, as it's been doing in many choices for interface, multiprocess Electrolysis work, etc.), it's less clear what to do. I can deliver a version that works with the current Firefox, but I couldn't promise in a contract that it'll continue to work with as yet unreleased versions. If I deliver a site tested with Firefox 6 today (and tested, but not certified, with the FF7 branch) then it'll still sound out of date by the end of the year when we're all on FF9 or FF10.

      Mozilla's answer is that we should all just forget about version numbers and trust that the stream of updates probably won't break things (and if it does it'll be for good reasons -- honest). All well and good but doesn't fit with the way many organisations manage things. Since 4.0, I've stopped evangelizing about Firefox; Mozilla have become yet another software company who cause me grief rather than something to be proud of.

    15. Re:Why not just wait for version 7? by Grishnakh · · Score: 1

      Since 4.0, I've stopped evangelizing about Firefox; Mozilla have become yet another software company who cause me grief rather than something to be proud of.

      Mozilla, Gnome, Ubuntu... the whole free-software world seems to be self-destructing. It's almost like they're trying to drive people back to proprietary software by bungling things as much as possible.

  4. Wow already v6 by Anonymous Coward · · Score: 0

    Takes time to change that number from 5 to 6. Those hard-working devs has to
    first delete the old 5, and then find the 6 on the keyboard, and then press the 6.

    I'm exhausted just thinking about all the high-quality gruesome work they do for us.

    1. Re:Wow already v6 by Anonymous Coward · · Score: 0

      Like that doesn't make it less retarded.

    2. Re:Wow already v6 by iggymanz · · Score: 2

      the relevant sarcastic question would be "And how many applications used by millions of pissed people have you released again and again, jacking up the major version number in rapid succession"

    3. Re:Wow already v6 by Cyko_01 · · Score: 2

      you have clearly not been following development. --> https://developer.mozilla.org/en/Firefox_6_for_developers

    4. Re:Wow already v6 by Anonymous Coward · · Score: 0

      "knows what they're doing".

      They have jumped the shark.

    5. Re:Wow already v6 by Anonymous Coward · · Score: 0

      That's true, i havent. But i shouldnt have to, improvements should come in two forms,
      either silently improving things under the hood. Or give users nice new features.

      Currently, from my point of view, Mozilla creates each browser more bloated then the
      previous. And they comes with annoying new mis-features. And Mozilla happily announce
      these things with big fake versioning numbers and expect people to be *happy*.

      I'm sorry. There's fantastic work going on too i'm sure. It's truly sad that thier work
      goes unnoticed because there's clowns who sabotages things.

  5. Plugins by Allicorn · · Score: 5, Informative

    Unfortunately six of the plugins I rely on (yes, those plugins that are supposedly the #1 reason to use Firefox over less customizable browsers) don't yet even support Firefox 5. Everytime that "update Firefox" box comes up, I check, find six plugins outstanding, and back out of it.

    Update too fast and you will leave users behind.

    --
    OMG!!! Ponies!!!
    1. Re:Plugins by Anonymous Coward · · Score: 0

      Between Ubuntu and Firefox "upgrading" the user experience into oblivion, Microsoft is starting to look like the voice of reason and sanity. The who computing ecosystem is being torn apart and turned on it's head.

    2. Re:Plugins by pep939 · · Score: 1

      Update too fast and you will leave users behind.

      I don't get the point either... We just updated to FF 5, how come they're pushing version 6 already? Are they trying to get ahead of IE in version numbers?

      I'm still running FF 3.5.X like a charm on most desktops, and having tested a Beta a couple of weeks ago, I don't see how they justify being at version 6 now.

    3. Re:Plugins by EMR · · Score: 5, Informative

      This is why they are encouraging extension developers to switch to the Mozilla addons SDK which provides API stability between firefox releases (and is built in in firefox 4.0+ ). the addon SDK also allows for installing plugins without restarting the browser!! YEAH!!!

      now, have you tried installing the addon compatibility reporter?

        https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/

      with that enabled you can forcibly enable addons that claim to not be compatible and test to see if they work. Also it gives you a away to send feedback to the developer that "hey it works" or "no it doesn't". And of course if you haven't contacted the developers of those addons, then that could be why they haven't been updated.

    4. Re:Plugins by Co0Ps · · Score: 0

      +1 Informative

    5. Re:Plugins by haruchai · · Score: 2

      Do you mean plugins or add-ons? If you're referring to addons / extensions, do they work if you turn off version checking?
      http://kb.mozillazine.org/Extensions.checkCompatibility

      --
      Pain is merely failure leaving the body
    6. Re:Plugins by iggymanz · · Score: 4, Insightful

      well isn't that special, the user is supposed to spend lots of time each quarter and hope they come up with the right tests to check everything? apparently, some of the add-on developers don't like that schedule either.

          that's the exciting new trend spreading across the major open source projects, disruptive but half-baked changes. Ubuntu with Unity, GNOME, KDE, Firefox. What other major project will have its developers flip the users the bird and fly off into the Land of Un-Usability? stay tuned, there really are a couple more in the pipe.....

    7. Re:Plugins by Bryan+Bytehead · · Score: 1

      Good grief.

        Install the Nightly Tester Tools. Just because Mozilla (actually the extension) says that it's unsupported doesn't mean it won't work. I've got a couple of extensions that are limited to 3.*, and THOSE still work. And of the ones that don't tend to work, those authors have made available beta versions that haven't broken anything for me yet.

      And I'm running the 8.0A1 nightly 64-bit. The only plugin (and I do mean plugin, not extension) that won't work is the WMP plugin. The 32-bit version works just fine, even 8.0A1.

      --
      Bryan
    8. Re:Plugins by Anonymous Coward · · Score: 0, Funny

      Did you somehow miss what M$ has been doing to the user interface lately?

      There is but one option if you don't want your user interface completely fucked these days. Apple.

    9. Re:Plugins by DesScorp · · Score: 5, Interesting

      Unfortunately six of the plugins I rely on (yes, those plugins that are supposedly the #1 reason to use Firefox over less customizable browsers) don't yet even support Firefox 5. Everytime that "update Firefox" box comes up, I check, find six plugins outstanding, and back out of it.

      Update too fast and you will leave users behind.

      I used to encourage Firefox use in my shop... I gave my users the choice of IE and Firefox, and back when IE had that huge list of old unpatched holes, I told my users that I preferred FireFox if they were so inclined.

      I've taken FF off of the approved list. The upgrades are coming too fast, and breaking too many things (mostly plugins, as the parent poster noted).

      --
      Life is hard, and the world is cruel
    10. Re:Plugins by vlueboy · · Score: 1

      This!
      I hadn't considered that in a while... OS X is the only mainstream OS that makes changes subtle. Except for updating the brushed metal pattern every couple releases to some other fill-in, it's almost been a GUI luddite because the Doc keeps the same location, size and main form. When they do something like adding those Download / Recent document stacking thingies, they avoid clashing with the rest of the GUI.

      What matters most is that for a full decade they avoided the huge Luna-like buttons, and won't be pulling an Ubuntu left->right tantrum. They've even resisted adding new window buttons and 3D-fying the the buttons, which is a Windows-related perversion to convey "change" and "improvement" in today's GUIs when features don't change that much. Last but not least, you don't need to relearn the Mac control panel every year. Vista to Windows 7 started to staedy the locations and labels a little bit , but I won't hold my breath with the myriad of netbook-imitating changes that a Windows 8 Metro GUI will doubtless bring

    11. Re:Plugins by Anonymous Coward · · Score: 0

      Why don't addons come with test suites and a manifest that says what APIs they use? Then they could be bumped to new versions automatically if they pass.

    12. Re:Plugins by visualight · · Score: 2

      Are you fucking kidding? There's an EIGHT? There's a sane fork of firefox somewhere, I'll find it.

      --
      Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
    13. Re:Plugins by Anonymous Coward · · Score: 0

      fuck you and fuck "this!!!" can't stand that shit. this. this this this.... fucking annoying.

    14. Re:Plugins by fluffy99 · · Score: 1

      This!
      I hadn't considered that in a while... OS X is the only mainstream OS that makes changes subtle

      That's because Apple recognizes that the average consumer wants consistency and stability, not new bling and features every few months. The consistency and reliability is also the main reason IOS apps are generally perceived to be of higher quality than Android apps

    15. Re:Plugins by PsychoSlashDot · · Score: 1

      fuck you and fuck "this!!!"

      can't stand that shit. this. this this this.... fucking annoying.

      Could be worse; it could be "me too". Or "+1".

      Understand you live in an era where people have a historically unprecedented ability to express their opinions that nobody gives a fuck about. Why don't you do like the rest of us and just ignore everyone else?

      --
      "Oh no... he found the .sig setting."
    16. Re:Plugins by Tharsman · · Score: 1

      Talking about that annoying message, is there a Firefox Addon for Firefox 4 that automatically closes that upgrade box? That spammy upgrade dialog box has been the reason for me to stop using Firefox unless I am in need of using one of those plugins.

    17. Re:Plugins by asa · · Score: 4, Informative

      Mozilla's good enough to manually scan all add-ons hosted at addons.mozilla.org and bump compatibility on any that don't use APIs which have changed. We have over 90% compatibility with AMO hosted add-ons that way. Unfortunately, not all add-ons are hosted at AMO and even though AMO makes the scanning tools available to anyone, many not-hosted-at-AMO add-ons don't avail themselves of this option.

    18. Re:Plugins by ColdWetDog · · Score: 1

      Are you fucking kidding? There's an EIGHT? There's a sane fork of firefox somewhere, I'll find it.

      That's nothing. Mine goes to 11.

      --
      Faster! Faster! Faster would be better!
    19. Re:Plugins by MightyMartian · · Score: 1

      Because IE9 looks so much like IE7 and IE8...

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    20. Re:Plugins by Anonymous Coward · · Score: 0

      Sure. 8 comes after 7, which comes after Firefox XP, which comes after Firefox 2000, which comes after Firefox 98, which comes after Firefox 95.

    21. Re:Plugins by GooberToo · · Score: 0

      That's pretty weak.

      Let me guess, you buy a new car and house every year? Do you throw your kids out every year too? Just because a new release is available doesn't mean you need to upgrade. Just because you screwed your wife nine months ago doesn't mean you need to throw your one year old out.

    22. Re:Plugins by TClevenger · · Score: 2

      Well, since Mozilla ended security patch support for Firefox 4 just three months after releasing it, who's throwing out what again?

    23. Re:Plugins by Anonymous Coward · · Score: 0

      I'll even buy one.

    24. Re:Plugins by Anonymous Coward · · Score: 0

      Why, after so many years, do so many Firefox enthusiasts not know the difference between plugins and extensions?
      They're not the same thing. They work differently.
      The difference really really matters. Just ask people trying to run Flash on less-popular platforms.

    25. Re:Plugins by Tridus · · Score: 1

      Remind me where I can get the version of Firefox 4 that still has security fixes being made for it again?

      Oh, right. They call that Internet Explorer.

      --
      -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    26. Re:Plugins by Anonymous Coward · · Score: 0

      ...or I could just use Chrome.

      Which is the same reason why everyone else is starting to use it, incidentally. Neither developers nor users feel they should be putting up with this bullshit, but Asa and the rest of the turds sure seem to think so! The Mozilla Foundation seems bent on making Firefox into a carbon copy of Chrome, save for the memory leaks that they refuse to acknowledge exist and whatnot.

    27. Re:Plugins by LinuxIsGarbage · · Score: 1

      After years of requiring IE6 for Web Apps, work finally officially encouraged Firefox 3.6 for Internet usage and pushed it through their central software manager. That was only a couple months ago and now its more hopelessly obsolete than IE6.

    28. Re:Plugins by Anonymous Coward · · Score: 0

      And the sad thing is people refuse to invest anytime finding solutions. In the amount of time it took to write your complain you might have been able to fix your issue. I have extensions that have not been update since FF 3 and they work fine. Of course it took a minute of googling to find extensions.checkCompatibility.5.0 but hey, it is much easier to complain.

    29. Re:Plugins by aliquis · · Score: 1

      What plugins do you have?

      I only need three.

      No-script, adblock plus, flash-block.

      In Opera I need none.

    30. Re:Plugins by Anonymous Coward · · Score: 0

      Why, after so many years, do so many Firefox enthusiasts not know the difference between plugins and extensions?

      Maybe because people just want to use their favourite websites without having to be browser "enthusiasts"?

    31. Re:Plugins by Anonymous Coward · · Score: 0

      So, stick with Firefox 3.6. I'm running every version from 3.6 and up on various machines and the only difference I see is that things are slower on the older versions.
      3.6 is a really nice browser.

    32. Re:Plugins by Anonymous Coward · · Score: 0

      That's why I finally switched to Mac. I need a unix desktop that actually works. I've been die hard Linux since like '99 but it just never gets better. Always in a constant state of FUBAR. Sure, Linux is still king as a server but I don't need a server at this time.

    33. Re:Plugins by Anonymous Coward · · Score: 0

      I'm also starting to agree with this, and I've been using Firefox since it was called Phoenix... Not a fan of some of the UI changes in the pipe either.

    34. Re:Plugins by iggymanz · · Score: 1

      my wife and kids have macs, but I find "using the unix" in it a bit weird from the command line. also one thing that annoys the hell out of me is that the fsck doesn't fix all hfs filesystem problems, but there are some third party wares costing money that can.

    35. Re:Plugins by Anonymous Coward · · Score: 0

      Pretty sure its a little far fetched to dare comparing Firefox to Unity and G3.
      Firefox evolves and did not redefine the browser paradigm like Unity or G3.

    36. Re:Plugins by marcello_dl · · Score: 1

      if you don't like upgrades breaking things up, debian stable has firefox 3.5.xx :)

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    37. Re:Plugins by KingMotley · · Score: 1

      Where can I get an upgrade to my wife every 6-8 weeks?

    38. Re:Plugins by Inda · · Score: 1

      We want nine!

      Then we want ten!

      Because ten is better than IE9!

      The version numbers are not for us.

      --
      This post contains benzene, nitrosamines, formaldehyde and hydrogen cyanide.
    39. Re:Plugins by arth1 · · Score: 2

      Amen. Breaking plugins every six weeks isn't going to make your users stay, nor get the plugin developers to bother making plugins for Firefox anymore.
      One of the plugins I used to use, from a rather large company, is no more with FF 5 and newer. They decided to stop supporting Firefox, and I don't blame them at all - when your own product is on a yearly release schedule, there's simply no way to keep up with Firefox. To do so, even if they could allocate resources outside schedule, would mean dropping decent QA and winging it.

      Mozilla have shot themselves in the foot with this one. Saying you don't care about corporate customers and only the millions of end users is all well and fine, but when the corporations drop Firefox support as a result, the end users will start to leave too. It's happening right now.

    40. Re:Plugins by arth1 · · Score: 1

      Could be worse; it could be "me too". Or "+1".

      Understand you live in an era where people have a historically unprecedented ability to express their opinions that nobody gives a fuck about. Why don't you do like the rest of us and just ignore everyone else?

      AOL!

    41. Re:Plugins by arth1 · · Score: 1

      Install the Nightly Tester Tools. Just because Mozilla (actually the extension) says that it's unsupported doesn't mean it won't work

      No, but unsupported means that the vendor won't support it.
      So the choices are really to run business critical software without support, or switch to a different browser. Which, of course, I will do both at work and at home, because I like consistency.
      Thanks, Asa, for making the choice easy.

    42. Re:Plugins by iggymanz · · Score: 1

      firefox has mutated grossly within a single generation, and is trying to redefine the browser paradigm, badly.

    43. Re:Plugins by arth1 · · Score: 1

      There's Seamonkey, which is the successor to the old Mozilla Suite. And strangely enough, it's less bloated and less dumbed down at the same time.

      I think 2011 is just the year of bumping the major. We now also have Linux 3.0.0 with so few changes from 2.6.40 that it normally wouldn't even be worth going to 2.8 over.
      Soon we'll see Apache 3.0, ssh 3 and gcc 5. With no real changes except making things incompatible.

    44. Re:Plugins by Anonymous Coward · · Score: 0

      No offense but how did you manage to cause "file system problems" on a Mac? Short of hardware failure it's pretty hard to screw up....

    45. Re:Plugins by gmhowell · · Score: 1

      All true, but unfortunately, I need to relearn which way the scroll wheel on my mouse works.

      --
      Jesus was all right but his disciples were thick and ordinary. -John Lennon
    46. Re:Plugins by LordLimecat · · Score: 1

      Dunno, if theyve made changes that will result in more compatible and stable addons with less work between upgrades, and all the addon dev has to do is one conversion, sounds like it is their fault if the thing doesnt work.

      I mean, chrome autoupgrades constantly, and im on the dev version, and ive NEVER gotten a notification about an incompatible addon.

    47. Re:Plugins by PPCAvenger · · Score: 1

      As stated below you could use the compatibility reporter extension or you can just do the following.

        1)Type about:config into the URL field.
        2)Context Menu > New > Boolean
        3) type: extensions.checkCompatibility.X.x
        4)Set the value to False

        Where X.x is the version number of the browser you want to override (e.g.. 5.0, 5.1, 5.2 or 6.0, 6.1, 6.2, etc..).

        See http://kb.mozillazine.org/Extensions.checkCompatibility for more details.

        That is essentially what the compatibility reporter extensions does though it also allows you to report to Mozilla whether a flagged extension works or not.

    48. Re:Plugins by Anonymous Coward · · Score: 0

      More often then not I just edit the install.rdf of the plugin and change the MaxVersion to something higher, most plugins will work fine, it's not like mozilla released any major code revisions recently.

    49. Re:Plugins by hcs_$reboot · · Score: 1

      Since we are talking about extensions (not actual plugins), note that usually the extension install.rdf file (in the .xpi / extension directory) may be edited and have its

      <em:maxVersion>

      tag increased. e.g. <em:maxVersion>4.*</em:maxVersion> => <em:maxVersion>6.*</em:maxVersion>

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    50. Re:Plugins by dakameleon · · Score: 2

      Buh? Have you seen 10.7 yet?

      - The sidebar has been given a mystifying bath to get rid of any hints of colour, so you have to actually look at the shape or read the word before clicking
      - "Devices" isn't there by default, and when you restore it's at the bottom of the sidebar, unlike every release of OS X up until now.
      - Where'd my scrollbar go? Why am I scrolling the wrong way?
      - Luna-like buttons? Weren't they a poor imitation of Aqua? Not that that is still there... all hints of Aqua's 3D-popping is gone for flat rounded corners (not necessarily a bad thing...)
      - There's a new window button to go "Full Screen". But it's not consistent - the app has to support it. So you can't expect the feature on all your old apps.
      - "System Preferences have been shuffled, consolidated, and renamed in every major releases of Mac OS X. Lion doesn't disappoint." http://arstechnica.com/apple/reviews/2011/07/mac-os-x-10-7.ars/17

      You can say Apple's interface is better, but you can't say it's stable.

      --
      Man who leaps off cliff jumps to conclusion.
    51. Re:Plugins by dakameleon · · Score: 1
      --
      Man who leaps off cliff jumps to conclusion.
    52. Re:Plugins by dakameleon · · Score: 1

      Are you fucking kidding? There's an EIGHT? There's a sane fork of firefox somewhere, I'll find it.

      That's nothing. Mine goes to 11.

      Given Chrome's already on 13 for its stable release, and 15 for its "Canary" release... 11's nothing!

      --
      Man who leaps off cliff jumps to conclusion.
    53. Re:Plugins by daver00 · · Score: 1

      Yes because reversing the default scrolling direction for everyone and completely overhauling expose is just a 'subtle' change...

    54. Re:Plugins by daver00 · · Score: 1

      Great theory but you should really give Lion a try, it almost the very definition of "new bling and features" and has introduced a non-trivial amount of instability for many users.

    55. Re:Plugins by dudpixel · · Score: 1

      Unfortunately six of the plugins I rely on (yes, those plugins that are supposedly the #1 reason to use Firefox over less customizable browsers) don't yet even support Firefox 5. Everytime that "update Firefox" box comes up, I check, find six plugins outstanding, and back out of it.

      Update too fast and you will leave users behind.

      Does chrome suffer the same fate? Chrome does allow plugins and it appears to be their quick release schedule that has prompted mozilla to do the same...

      --
      This seemed like a reasonable sig at the time.
    56. Re:Plugins by Doctor_Jest · · Score: 1

      As for "natural scrolling" I swapped it back to the original scrolling. But I actually like the new expose. It puts the multiple desktop and windows in one place. I don't use multiple desktops even in Linux. They are convenient at first, but they generally become a chore as you work... To each his own, I guess. Lion has been a fairly stable upgrade for me... but then again, I compare all my OS X updates to Tiger (that fiasco)... so they're ALL always better than Tiger. :)

      --
      It's the Stay-Puft Marshmallow Man.
    57. Re:Plugins by Anonymous Coward · · Score: 0

      The difference between Firefox and Ubuntu, Unity, Gnome, KDE, and co. is that Firefox used to be actually relevant. The others can't be going downhill because they were never above the ground in the first place.

    58. Re:Plugins by JImbob0i0 · · Score: 1

      3.5 is EOL with known security issues... at least be on the 'old stable' of 3.6.X (3.6.20 security update due soon)...

    59. Re:Plugins by Anonymous Coward · · Score: 0

      Joomla! (www.joomla.org)

    60. Re:Plugins by pep939 · · Score: 1

      Yeah, I know.... *ashamed*
      Blame Debian. *whistles*

    61. Re:Plugins by EdgeCreeper · · Score: 1

      that's the exciting new trend spreading across the major open source projects, disruptive but half-baked changes. Ubuntu with Unity, GNOME, KDE, Firefox. What other major project will have its developers flip the users the bird and fly off into the Land of Un-Usability? stay tuned, there really are a couple more in the pipe.....

      Well, I would have to ask, why?

    62. Re:Plugins by Anonymous Coward · · Score: 0

      Exactly, I got en email from the mozilla-dev center that basically said "We ran HistoryBlock against Firefox up-to-8 and it looks good, so we changed the install.rdf for your latest release as such."

    63. Re:Plugins by surgen · · Score: 1

      There is but one option if you don't want your user interface completely fucked these days. Apple.

      Until the ever-contracting distance between the different shades of grey in the OSX UI converge.

    64. Re:Plugins by Anonymous Coward · · Score: 0

      You mean like the Lion update to OSX?

    65. Re:Plugins by Grishnakh · · Score: 1

      Did you somehow miss what M$ has been doing to the user interface lately?

      I guess I must be missing something, because I don't see anything significantly different about the M$ user interface. My work laptop has Windows 7 pre-installed on it (I normally boot into Linux Mint, but W7 is there for the occasional Windows-only software I might need to run). It looks a lot like XP: there's a bar at the bottom, an icon you click on to bring up a menu (instead of saying "Start", it's just an icon, like in KDE or Gnome 1), that menu has all your applications on it, and the applications are horribly organized just like in XP instead of being sensibly organized by function as they are in KDE. Open windows have associated icons on the bottom bar just like in XP and KDE, except that in W7 they don't have the names or other textual information, only icons.

      I'm not particularly enamored of it (KDE is much nicer), but I don't see how it's all that different from WinXP.

      Now I've heard some vague rumors about Windows 8 copying the Unity and Gnome3 shenanigans, but for now those are only rumors. You can't buy Windows 8, as it's not released yet, and probably won't be for some time. Remember, before Vista was released, there was all kinds of talk from MS about how Vista was going to include something called "WinFS". Well that was many years ago and WinFS obviously was just vapor, so there's no point in getting excited about anything else MS leaks about upcoming versions either; just wait until they're really out and see then what's actually in them. I seriously doubt MS is going to do anything that might upset their corporate customers, and a gigantic UI change a la Unity would do exactly that, for all the countless corporations that have armies of drones using Dell desktop PCs to run MS Office and Outlook. If MS does do any Unity-like UIs, they'll probably do the smart thing (unlike the Gnome and Unity morons), and make it an option, or only for a tablet-based version of Windows while leaving their regular desktop UI relatively unchanged.

    66. Re:Plugins by Grishnakh · · Score: 1

      but I won't hold my breath with the myriad of netbook-imitating changes that a Windows 8 Metro GUI will doubtless bring

      I wouldn't be so sure. Microsoft was flapping their lips left and right about "WinFS" before Vista came out, and that obviously didn't materialize. They're always talking up stuff, and then when they actually release something, it's totally different. I bet Win8 will be just another warmed-over version of Win7, with a few evolutionary changes.

      Heck, Win7 is barely any different from XP from what I can tell. The icons are different of course, the entries on the bottom panel for running programs only have icons instead of text from the titlebar, it's ugly in a new and different way from XP, but otherwise it's pretty much the same. They didn't seem to change much about the way it worked, only the way it looks.

      Who knows, maybe MS will actually do something intelligent and make the netbook GUI a user option, or a different version of Windows aimed at Netbooks, while leaving the regular desktop GUI alone to avoid pissing off all their corporate customers. Corporations aren't going to like it if MS tries to foist a crappy netbook GUI on all their Outlook and Office-using office drones.

    67. Re:Plugins by Kremmy · · Score: 1

      I wish you were correct, I really do. But you're so dead wrong that I can't believe you even said that. Go take a look at recent Apple releases. Look at what they did to Final Cut Pro. Read up on how they made a hybrid of Express and Pro, removed the ability to load older project files, made massive changes to the user interface, basically told the entire top tier of the film editing industry that uses Final Cut Pro to go fuck themselves.

      It gets worse.

      If your spill your drink on your recent Mac laptop, it's gone. Toast. Number one priority in such an event is to pull the battery and let the thing dry out. REMOVE POWER. But you can't, because the battery is SCREWED INSIDE. It is designed to fail by the silliest little misstep that happens all the damn time. I had a Dell laptop get 32 ounces of water poured right into it, I pulled the battery immediately and let it dry, it worked fine for years after. My friend recently spilled a drink on their Mactop, and there wasn't an option, that's it, it's done. Bzzzzzt.

      Apple is screwing their users just as hard as everyone else is these days. We have a lot of room for progress out there, but the large players have utterly failed us at this point.

    68. Re:Plugins by Grishnakh · · Score: 1

      IE is at version 9, while FF is only at version 5 (soon 6), so obviously IE is a more mature and advanced product....

  6. Major versions? by RoFLKOPTr · · Score: 2

    I still don't understand why they elected to change to this system of releasing major versions every flippin month. The old system was working just fine, why can't this be Fx 5.5? And save v6 for when there are actually some major changes that deserve a major version.

    1. Re:Major versions? by the-matt-mobile · · Score: 1

      No doubt. When I read the OP, all I could think of was that of was what an understatement it is to say they released version 6 early when you consider that 4.0 came out a few months ago. Given all the really bad decisions Mozilla has made lately, I have to wonder if they've ever heard of this little old browser called Netscape? History seems to be repeating itself.

    2. Re:Major versions? by ceoyoyo · · Score: 4, Insightful

      Because incrementing by full version numbers gives them an excuse to break things at every release.

    3. Re:Major versions? by ThePhilips · · Score: 3, Interesting

      Exactly. Meaning that if one wants stability, FireFox and Chrome are probably not for them.

      IE and Opera started looking so much more attractive now. Even Netscape 4.7...

      --
      All hope abandon ye who enter here.
    4. Re:Major versions? by linebackn · · Score: 1

      For those that may not remember, there used to be quite a bit of fanfare with Firefox community "parties", special downloading events, and such surrounding the major releases.

      I suspect the intent was to try and recapture this publicity at more frequent intervals.

      Unfortunately this has instead made major releases meaningless while destroying long term support and creating problems with many extensions.

    5. Re:Major versions? by Anonymous Coward · · Score: 0

      Funny, you think Mozilla is making bad decisions, and I (and most) think they've been improving the browser tremendously the past few releases.

      Quicker, more responsive, improved and less wasteful user interface, and reduced memory (in version 7).

      Yes, such bad decisions.

      Of course, I know these great things in your mind don't make up for "tabs on top" or "I don't like the numbers they're using" or whatever other trite irrelevant bike-shedding nonsense you people are complaining about today.

    6. Re:Major versions? by aitan · · Score: 1

      Opera is also releasing new versions very fast.
      The only difference is that they keep using the. 5 versions although they add lots of changes in each release

    7. Re:Major versions? by DarkXale · · Score: 1

      Like Microsoft's cakes they sent to the Firefox team being downgraded to cupcakes?

    8. Re:Major versions? by LinuxIsGarbage · · Score: 1

      This way Microsoft can save money. They just buy one package of cupcakes and send out one cupcake for every Firefox version. They will finish a box of cupcakes before they go stale.

    9. Re:Major versions? by Anonymous Coward · · Score: 0

      Given all the really bad decisions Mozilla has made lately, I have to wonder if they've ever heard of this little old browser called Netscape? History seems to be repeating itself.

      Netscape Navigator was major version 3 for a good long time and upgraded to version 4 ("Communicator"), which stayed at major version 4 for a good long time. The first go at Netscape 5 was thrown out pre-alpha and the next became the first Mozilla Milestone release. All of the later "Netscape" releases were AOL-sodomized copies of Mozilla pre-beta releases and had nothing to do with Netscape, so what's the point of bringing it up?

    10. Re:Major versions? by Anonymous Coward · · Score: 0

      Funny, you think Mozilla is making bad decisions, and I (and most) think they've been improving the browser tremendously the past few releases. Quicker, more responsive, improved and less wasteful user interface, and reduced memory (in version 7).

      And it all couldn't have been done without calling it a new major version. They tried to call it "Firefox 4.3" but it slowed down, used more memory, and the interface widgets turned to Motif until they raised the major version number.

    11. Re:Major versions? by Anonymous Coward · · Score: 0

      The real reason is, they want to be the one FF with the highest version number, and Square is already at version 14. Of course, they'll never admit it...

    12. Re:Major versions? by LordLimecat · · Score: 1

      Meaning that if one wants stability, ... Chrome is probably not for them.

      Yea, citation needed.
      A) Whens the last time an addon or plugin has stopped working, even in bleeding edge dev versions of chrome? MAYBE back at v4 or 5 when they were still hammering out extensions.
      B) IE is most definately not "more stable". Upgrading it is likely to break a zillion things, not just webpages or plugins either. And its silly to talk about addon stability in a browser that doesnt even support addons.
      C) Opera has like a 2% market share. Telling mozilla with its 25% share "you need to emulate this guy who has never been relevant in the desktop sphere" is kind of counterintuitive.

    13. Re:Major versions? by Leafheart · · Score: 1

      I still don't understand why they elected to change to this system of releasing major versions every flippin month. The old system was working just fine, why can't this be Fx 5.5? And save v6 for when there are actually some major changes that deserve a major version.

      Because when I an user check the "Choose your Browse" screen, it wants the higher number. Pfff, are you on FF5? My Chrome goes to 11!

      --
      --- "When you gotta do something wrong. You gotta do it right. (Fighter)"
    14. Re:Major versions? by ThePhilips · · Score: 1

      Meaning that if one wants stability, ... Chrome is probably not for them.

      Yea, citation needed. A) Whens the last time an addon or plugin has stopped working, even in bleeding edge dev versions of chrome? MAYBE back at v4 or 5 when they were still hammering out extensions.

      Extensions are irrelevant to stability as enterprise deployments go. What matters is that one can rely on release schedule.

      Simple truth: you can't say "this website was tested and guaranteed to work with version NNN of Chrome/FireFox". Because the versions become obsolete by the time users get around to start using it.

      And more users are forced to use IE in the office, more would switch to IE at home.

      B) IE is most definately not "more stable". Upgrading it is likely to break a zillion things, not just webpages or plugins either. And its silly to talk about addon stability in a browser that doesnt even support addons.

      It is. I'm not aware of the breakages you speak of. Our tests (using several web based products we sell) do not indicate anything of the sorts. (Yes, IE sucks, but it sucks in a backward-compatible fashion.) Otherwise, (1) MS doesn't release all-changing radical updates with minor versions; (2) MS supports old IE versions for very long time after release.

      C) Opera has like a 2% market share. Telling mozilla with its 25% share "you need to emulate this guy who has never been relevant in the desktop sphere" is kind of counterintuitive.

      Yes. I sort of agree. But you forget about the elephant in the room - IE.

      The problem is that now we have two nearly identical browsers on the market - Chrome and FireFox. Competition has decreased and we have lost the only IE's viable alternative, leaving us with not so viable alternative - the Opera. And the decrease in competition is what I'm against of.

      --
      All hope abandon ye who enter here.
    15. Re:Major versions? by LordLimecat · · Score: 1

      It is. I'm not aware of the breakages you speak of. Our tests (using several web based products we sell) do not indicate anything of the sorts

      Move from IE8 to IE9 and watch in amazement as 3rd party OS apps break. And if you dont think there are IE reliant webpages that dont break catastrophically on upgrade, you are badly mistaken-- I just had to roll back one of the first upgrades I did in a soho company.

      Chrome upgrades are probably more of an issue for large companies, but I mostly deal with 1-100 user companies, and its never an issue. Maybe 1 out of 20 folks have an issue, and its small enough that I can do ietab or something similar. Its a good tradeoff for me, since IE means I need to constantly watch acrobat and java and flash versions for vulnerabilities; chrome takes care of that and blocks insecure plugins. I would far rather deal with the odd incompatible website than the odd userland rootkit.

    16. Re:Major versions? by shutdown+-p+now · · Score: 1

      I don't know about Chrome. Despite going through many major version updates, all my Chrome extensions just keep working. And they don't change UI nearly as much as FF.

    17. Re:Major versions? by Anonymous Coward · · Score: 0

      I've been using Chrome since 6.0, and I've never had a plugin break on upgrading (currently running Chrome 13).

      When FF 4 came out, I temporarily switched back to it, but when FF 5 came out just after that, several plugins stopped working (I used the compatibility reporter to force FF to run them in the new version).

      I'm a big fan of free (as in speech) software, but IMHO Chrome is currently just better than FF.

    18. Re:Major versions? by ThePhilips · · Score: 1

      It is. I'm not aware of the breakages you speak of. Our tests (using several web based products we sell) do not indicate anything of the sorts

      Move from IE8 to IE9 and watch in amazement as 3rd party OS apps break.

      Oh. That's a great point: MS doesn't forces you to update to IE9. And IE8 (likewise the IE7) are still supported and receive patches.

      Its a good tradeoff for me, since IE means I need to constantly watch acrobat and java and flash versions for vulnerabilities; chrome takes care of that and blocks insecure plugins. I would far rather deal with the odd incompatible website than the odd userland rootkit.

      ActiveX is a pain - despite the fact that it is more or less not used this days. Developers moved to Web-only tech, and throw the shit at fans this days.

      In the end, the problem is that "odd incompatible websites" often end-up being the favorite sites of a manager. Or crappy corpo-crapo-ware portal. You can't argue against neither.

      And when one tries to pitch security, managers act surprised - "we do not care, we already pay $$$$$ to AV company!"

      Best our IT could manage is to add FireFox to list of supported apps and allow to install it (via some proprietary enterprise deployment/update system). But we are still (and I wholeheartedly support it) on FireFox 3.6 as our IT is totally freaked out (as many others) about new Mozilla release strategy. (I doubt it is a sign of anything, but they have added Opera too few month ago.)

      --
      All hope abandon ye who enter here.
  7. Meanwhile... by Zakabog · · Score: 2

    Meanwhile most of the customers coming into my shop still run Firefox 3. Why are they releasing major versions so frequently, there's going to be a lot of people with very low Firefox version numbers that don't know they're 10 versions behind and wouldn't know how to fix that.

    1. Re:Meanwhile... by Samantha+Wright · · Score: 5, Informative

      I would suggest mentally normalizing the version numbers into release dates. Keep a list in your head, or on a wall, and then you can judge outdatedness more cromulently:

      • Firefox 1.0: November 9, 2004
      • Firefox 1.5: November 29, 2005
      • Firefox 2: October 24, 2006
      • Firefox 3: June 17, 2008
      • Firefox 3.5: June 30, 2009
      • Firefox 3.6: January 21, 2010
      • Firefox 4: March 22, 2011
      • Firefox 5: June 21, 2011
      • Firefox 6: August 16, 2011

      Now, you can truthfully ask yourself "How outdated is this user?" rather than the bogus proxy question "How many versions behind is this user?"

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:Meanwhile... by Anonymous Coward · · Score: 0

      Because at the rate they're going, Firefox 8 will be released 3 months ago.

    3. Re:Meanwhile... by Zakabog · · Score: 2

      That'd be easier to do if instead of Firefox 6 they called it FIrefox 11-8 (2011, Aug.) That way they can release multiple editions on their quick schedule and you'd know the year and month it was released just by knowing the version number.

    4. Re:Meanwhile... by Anonymous Coward · · Score: 0

      Soon enough they will be releasing versions numbered by their Epoch time of release.

      FF 1.0: v1099958400
      FF 1.5: v1133222400
      FF 2.0: v1161648000
      FF 3.0: v1213660800
      FF 3.5: v1246320000
      FF 3.6: v1264032000
      FF 4: v1300752000
      FF 5: v1308614400
      FF 6: v1313452800

    5. Re:Meanwhile... by LordLimecat · · Score: 1

      Presumably, the goal (which is imminent, i believe) is that the updates will be automatic and invisible, so you never need to ask that question. For example-- whens the last time youve seen an out of date chrome browser?

    6. Re:Meanwhile... by Samantha+Wright · · Score: 1

      I concur—but given your line of work, it'd probably still pay off just to keep a printed list of the release dates.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    7. Re:Meanwhile... by Excelcia · · Score: 1

      Normalizing against dates would work if they kept updating old versions with security patches for a year or so like they used to. But they're not doing this any more. They are going "end of life" on each "major" release as soon as the next one is out, which means you fall behind by a version and it doesn't matter that it's only a month old, you don't get security patches any more.

      So sure, normalize against dates to see how "outdated" you are, but if your version is six months old, that's five months of security patches you're not getting.

      Mozilla's new system is just simply untenable.

    8. Re:Meanwhile... by Samantha+Wright · · Score: 1

      They're actually not that common in academia, where every lab has its own messy solution to everything. Nascent geeks turn off the auto-updater out of force of habit, and then graduate, leaving their less-literate successors with the version that was around at their time. If you hit up StatCounter Global Stats and browse the bar graphs by continent, you'll find that Africa, Asia, and South America all have substantial usage of Chrome 5.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    9. Re:Meanwhile... by Samantha+Wright · · Score: 1

      When they complete the shift to auto-updating, no one will be worried any longer, I don't think.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    10. Re:Meanwhile... by Anonymous Coward · · Score: 0

      That's just plain stupid.

      Firefox 3.6 is still getting updates.

    11. Re:Meanwhile... by PybusJ · · Score: 1

      It's not quite comparable. Earlier releases had security patches for a fair period after the next major version was released (FF 3.6, is I think still supported) Firefox 4 is already unsupported and as soon as version 6 gets released, FF5 goes unsupported immediately.

    12. Re:Meanwhile... by Samantha+Wright · · Score: 1

      Well... I think the concept is still compatible, you just need to expand the list to include all of the n.n.x releases.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    13. Re:Meanwhile... by PybusJ · · Score: 1

      But n.n.x releases were automatically applied; didn't look any different to users, and didn't break and functionality (such as add-ons).

      Users are quite used to applying security updates, but that's rather different from changing versions with potentially incompatible changes every 6 weeks.

    14. Re:Meanwhile... by Samantha+Wright · · Score: 1

      Okay... but I'm not seeing your point. Converting version numbers to dates is still a good handle of determining how out of date a user's computer is. Which is what we were talking about.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    15. Re:Meanwhile... by PybusJ · · Score: 1

      I'm just annoyed by all the "Mozilla haven't really changed anything, you just need to reinterpret the numbers" comments when they've actually made a major change to their process and what it means for users.

      I think your list above gives the wrong dates; it's the end-of-life dates that the shop owner should be using to judge outdatedness. The new release model creates EOL browsers like no-bodies business; though since they now automatically update people through major release numbers you shouldn't see so many random machines with FF4 or FF5. The downside of this is automatic change/breakage for users.

    16. Re:Meanwhile... by Samantha+Wright · · Score: 1

      Also a reasonable refinement. I encourage you or someone else with enough spare time to track down these dates and make them publicly known. Alas, I only have enough time and energy to scour so many Wikipedia articles.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    17. Re:Meanwhile... by PybusJ · · Score: 1

      http://en.wikipedia.org/wiki/History_of_Firefox#Release_history shows all the point releases. Given the speed at which vulnerabilities appear, shortly after the last point release seems a good approximation.

  8. Firefox has been fired. by Anonymous Coward · · Score: 1, Interesting

    I was a long-time Firefox user, I even was part of Spreadfirefox.com and was a "Zealot" that managed to convert my Mom and brother to it and when I was at college I got the IT admins to install it back in the bad old days of IE6. But Firefox has lost its way. Its peak was 1.0 to 3.6. The memory leaks, the obsessive addon breaking, the theft of the status bar and ignoring its users and wasting 80 million dollars a year is the last straw. I uninstalled Firefox this week, and have switched to Chrome on my main PCs and Safari on my iPad. I might even go back to IE when Windows 8 comes out due to the promising platform previews.

    Netscape died a horrible death, and Firefox seems to be repeating it. Hopefully enough concerned users fork the Firefox 3.6 code and "re-pheonix" it before it's too late.

  9. Stupid versioning scheme, really by Ragondux · · Score: 4, Funny

    They should really call it Firefox 1108, and release one per month. If that's too slow, they can just add the day too, Firefox 110816 sounds really advanced.

    1. Re:Stupid versioning scheme, really by ThePhilips · · Score: 1

      Or why not use unary numeral system for the version numbers? FireFox v111111 would confuse hell out of the competition. After all, Chrome, as of last morning is still at the measly v13.

      --
      All hope abandon ye who enter here.
    2. Re:Stupid versioning scheme, really by Anonymous Coward · · Score: 0

      Is that big-endian or little-endian?

    3. Re:Stupid versioning scheme, really by Anonymous Coward · · Score: 0

      Why is this modded funny? It's actually exactly the version numbering scheme that Mozilla needs, instead of abusing the major/minor numbering scheme. My company develops a Linux distribution with this rolling release technique, and we've been using a yy.mm.dd-rev numbering scheme for almost 10 years now.

    4. Re:Stupid versioning scheme, really by Excelcia · · Score: 1

      This is still too slow. They need 110816.0830(z)

    5. Re:Stupid versioning scheme, really by wstrucke · · Score: 1

      This whole versioning change is a really bone headed move on the part of mozilla. The old system worked well. Any time your marketing department starts to influence product development it's a very bad sign for your business. Doesn't anyone at Mozilla read dilbert?

    6. Re:Stupid versioning scheme, really by SydShamino · · Score: 1

      Won't that break with the Y2.1k bug?

      --
      It doesn't hurt to be nice.
    7. Re:Stupid versioning scheme, really by Ragondux · · Score: 1

      Nah, that's just an opportunity to go from 9912 to 210001 in one release.

  10. Version numbers by Anonymous Coward · · Score: 0

    So what exactly is this pressing need to increment one major version number per release? Does a higher number make the browser somehow better? What is wrong with the old and familiar scheme of major.minor.build (or a form of)?
    Looking up some differences between 5 and 6, I find the major version increment hardly warranted. I find this desire to catch up to Opera and Chrome in version numbers rather comical, how about we just increment major for every build? Hell, get rid of major and use build # as version: Firefox 2740.

    1. Re:Version numbers by hedwards · · Score: 1

      Firefox 6 is 1 better than Firefox 5, duh.

    2. Re:Version numbers by bussdriver · · Score: 1

      Version numbers have been bad for decades- marketing people wanting whole version numbers like 5.0 so update end up 5.0.1 and other silly games in the other direction.

      What they should be doing is Firefox #.build# so you get the feature set and the build number. They seem to forget developers make the web apps they run too! a whole version number should remain somewhat static as far as features that cause any noticeable changes and bug fixes can go into the build numbers. When they actually do something that impacts web developers and add-on developers then they should go up a whole version. They are partially doing this today, as each version upgrade seems to break everything.

    3. Re:Version numbers by Cyko_01 · · Score: 1

      The major version number (the first digit) does not symbolize major changes, but a stable release - which this is - only with fewer changes then fx2/3/4. It is even more stable then previous versions because every version goes through a much longer testing period then before, and a relatively short development period.

  11. Awkward moment.. by Anonymous Coward · · Score: 0

    When Mozilla actually releases something early instead of delaying everything.

  12. Version number issues by Anonymous Coward · · Score: 0

    Many companies that make software for the web usually have a policy of supporting browsers up to a certain version number.
    I think Mozilla needs to have an internal version number that reflects the stability of the rendering API so this way companies
    can have some sense of how compatible future versions of Firefox are.

    Where I work at , we only support Firefox 3.5 and 3.6 . The project that I am on has software where there are a few rendering
    issues and bugs that show up on FF4+, which we will not fix yet because our clients tend to be mostly IE users. And with
    Firefox adopting Chrome's update schedule, it's very hard to pin down what version of Firefox to support since we don't
    know what things will change, and don't have the luxury to schedule a block of time devoted to "beta testing" new versions
    of Firefox, if there are changes to the rendering or javascript engine that break previously working code.

    1. Re:Version number issues by Cyko_01 · · Score: 1

      in my experience, if it worked in the old version, it probably still works in the new version unless you used some stupid hack or workaround. The reverse is rarely true, so it might actually be better if you only the supported the old version

  13. Rolling Releases by Anonymous Coward · · Score: 0

    I thought the version numbers were rolling releases now? So doesn't the release of "6" just mean it's being released on the "5" stream?

    1. Re:Rolling Releases by CyberDragon777 · · Score: 3, Informative

      6 is released, 7 is in beta, 8 is testing (Aurora), 9 is trunk development (Nightly).

      6 weeks later:

      7 is released, 8 is in beta, 9 is testing, 10 is trunk development.

      etc.

      --
      We both said a lot of things that you are going to regret.
  14. Does Mozilla not read Slashdot? by linebackn · · Score: 5, Insightful

    I can understand companies not being in touch with their customers, but does Mozilla not even read tech sites like Slashdot? Every story about Firefox lately is filled with exactly how negatively people feel about this version number fiasco.

    Chrome was able to get away with bumping version numbers because it was a very new product and nobody was depending on it yet. Even though they removed the "beta" tag surprisingly early on (for a Google product), I think many people STILL consider Chome as "beta".

    On the other hand large corporate type applications were just beginning to support Firefox and depended on long term support of major versions. Well, that has just been stomped in the face. Sadly, from a corporate stand point the only browser that really seems stable, viable, and "corporate friendly" now is IE.

    1. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      The internet at large is full of negativity. Simple dissent is not enough reason to consider a change. Mozilla isn't a democracy, and it shouldn't be.

    2. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      SHUT UP SHUT UP SHUT UP! Speak no evil!

      - Mozilla developer. BTW, our next project is "Hear no evil", with a stone monkey for it's symbol. It's an internal project which will allow us to follow the "do no evil" motto of our Google masters. "See no Evil" is a public project. Everything renders white.

    3. Re:Does Mozilla not read Slashdot? by Rich0 · · Score: 4, Informative

      The other issue is that Chrome doesn't tie compatibility to version numbers. When I update Chrome I don't get a box telling me it is disabling half my extensions/apps. For the most part, everything just works. So, the number is just a number.

      Mozilla's problem is that they assume extensions don't work after major version changes, which basically imposes arbitrary breakage. So, the number isn't just a number in their case.

    4. Re:Does Mozilla not read Slashdot? by iggymanz · · Score: 1

      dissent due to breaking compatibility with tools users use, losing features they use, and hampering productivity are a reason to change. The internet is *filling* with negativity for firefox, caused by the loss of common sense by the Mozilla Corporation. It is reason enough to change to Seamonkey or Chrome.

    5. Re:Does Mozilla not read Slashdot? by visualight · · Score: 0

      Dude. 'EVERYONE' hates this shit. It isn't simple dissent.

      --
      Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
    6. Re:Does Mozilla not read Slashdot? by MightyMartian · · Score: 1

      This message brought to you by Firefox Fanboy version 24

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    7. Re:Does Mozilla not read Slashdot? by Anonymous+Brave+Guy · · Score: 1

      Sadly, from a corporate stand point the only browser that really seems stable, viable, and "corporate friendly" now is IE.

      I can't speak for anyone else, but we just reviewed our browser support policy for one of our clients, and I'm afraid Firefox has now joined Chrome on the "not supported" list. We aren't developing a public web site, we're developing control software for equipment that clients pay very large sums of money for. If we say we support a particular browser, that comes with serious strings attached, and that in turn means there has to be a stable version with reasonably long-term support expected that we can test against before we're willing to sign our names under a support contract for it.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    8. Re:Does Mozilla not read Slashdot? by FooBarWidget · · Score: 0

      Slashdotters always complain about stupid minor things like version numbers. I upgraded to Firefox 5 and Thunderbird 5 a while ago and holy shit it's insanely fast! But no, Slashdot prefers to complain about the version number. I'd say Mozilla should ignore the complaints. If that means the people who complain about Firefox's version number are driven away to Opera then good riddance. That'll just filter out all the bikeshedding so that Mozilla can focus on what really matters, like standards compliance, security and performance.

    9. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      The other issue is that Chrome doesn't tie compatibility to version numbers.

      Yes, Chrome does tie compatibility to version numbers, just not as a max version number like Firefox has instituted, but a minimum version number. In my manifest.json file for my Chrome extension I have "minimum_chrome_version": "9.0" since it uses a feature that wasn't available until 9.0.

      The reason this works well is because if they enable feature x in version y, you know a user that doesn't have that feature won't be able to install a broken plugin. At the same time, Chrome hasn't (as far as the API goes) removed anything from the tree, unless they had it in experimental, AFAIK. So they don't need the max version.

      I think this is something Chrome got right that Firefox has backwards. You can build a plugin, even using their new addon SDK mentioned above, and half the time it won't install on other users machine because they don't have the minimum version required, or don't have some variable set right in their configuration area. I think it's good that Firefox tries to make the SDK better, and I think their automated version upgrades for plugins is a good idea, but you shouldn't need an extra plugin to allow them to run if the developer didn't update.

    10. Re:Does Mozilla not read Slashdot? by Tridus · · Score: 1

      They do, in fact last time we had one of the devs basically apologizing for that idiot Asa.

      But most of Mozilla lives in an "I'm awesome!" echo chamber and they really don't understand why other people don't play along. I mean what other excuse is there for the abortion that is the Thunderbird 5 UI? No doubt to be fixed in Thunderbird 18. Maybe.

      This happens to projects sometimes. They just go off the pot and turn wacky. When that happens its time to go elsewhere.

      --
      -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    11. Re:Does Mozilla not read Slashdot? by Billly+Gates · · Score: 1

      If Asa was not an asshole about it and trolled users on slashdot begging them to use IE 8 for work when they went out and put their reputation at risk to bat for Firefox then yes it could be more corporate friendly.

      Chrome is not too bad for work either because the plugins do not break and you can manage it with group policies if you are still worried about it.

      The problem is after ... in the mind of the CIO ... we got burned with Firefox, how do we know Google wont do the same thing? They are not an enterprise player like good old Microsoft our friend from way back then.

      IE 8 also is the first version that is not plain horrible and is about at Firefox 2.x. No hacks needed with strange bugs. IE 9 supports basic HTML 5 and has beautiful hardware rendering with very smooth scrolling that is ahead of Chrome and Firefox and is about at Firefox 3.6. By next year IE 10 will be where Chrome is today and almost fully support the whole HTML 5 spec. So why not go with IE?

      It is not the piece of garbage it once was. I love the features of Chrome and Firefox over IE 9, but IE 9 is my favorite for simple browsing, as its awesome scrolling and hardware rendering. I am waiting for Firefox to catch up. Does anyone know if the alpha versions of Chrome or Firefox support DirectX better or as good as IE 9?

      So it looks like IE is going to have a return in the next few years sadly. I prefer more browsers but at least IE is in the same league as the other two. Mozilla blew it and could of gave IE a run for its money if Mozilla played their cards right. Many corporations have to keep IE 6 around for intranet apps and a second browser for the web would have been perfect.

    12. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      Read up about how dumb people think they have to stick with their decisions no matter what, because otherwise one might call them "flip-floppers" or something like that.

      Instead of, you know... being happy that one has learned from one's errors and is a better person now.

      Other than that, the only answer that I have is complete delusion. You know... the kind that seems to happen to everyone in power... who suddenly feels like it's all about him and he doesn't have to give a fuck about others anymore to get what he wants. Like those Wikipedia admins. Like pretty much all politicians and leaders ever.

      Problem is: It's a delusion. Which means it will all come down. And it will only be noticed when it's way too late. Or even never.

      So, of course I hope my predictions are wrong. But if not, I'd get out and fork ASAP. Because it will be a saaad sight when FF gets below 1% again, bloated and shitty, with 80% of the developers and 99.9% of the funding gone, and the last 20%, completely detached from reality, will still proclaim "It's the best browser on the planet! Whoohoo!", acting as if nothing changed.
      I've seen it happen to the lives of real people. You can't help them, since they'll ignore you, and they can't help themselves, since they think everything is alright, But it's not. Their life is horrible, and you have to watch it. All decades long...

    13. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      FooBarWidget, I am actually happy to hear Firefox is working great for you, but this rapid version number changing is causing VERY REAL problems for many people. Companies can not support a browser that makes major feature changes every few months, and it is messing up add ons for a lot of individuals.

      While you may not think it affects you now, I think you will soon see things like banking sites that go back to only supporting IE. It sucks, and shouldn't be that way but this is the real result of Mozilla's decision.

    14. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      Actually, everyone loves the direction that Firefox has been heading, from what I've seen. Quicker, more responsive, improved user interface, and less memory usage (with version 7). People clamor for this stuff all the time. Once people on Slashdot get over their irrational emotional responses to insignificant things, they'll realize that.

    15. Re:Does Mozilla not read Slashdot? by visualight · · Score: 1

      I know zero out of dozens of people that like the direction firefox is going in. None of them read slashdot. None of them post on forums or provide feedback in some other way.

      Firefox above 3.6 is BANNED at work. Don't think for a second that this doesn't affect browser choice at home.

      For the first time since I can remember "regular" users are having break room conversations about firefox vs. [anybrowser].

      YOU are living in your own bubble, not posters on slashdot.

      --
      Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
    16. Re:Does Mozilla not read Slashdot? by ThePhilips · · Score: 1

      Yep, I totally see how UI fsckup is required - to improve performance and memory consumption. Stick and carrot so to say.

      --
      All hope abandon ye who enter here.
    17. Re:Does Mozilla not read Slashdot? by FooBarWidget · · Score: 1

      I can understand it when people complain that extensions break, but banking websites dropping support for Firefx? Banking websites are built plain HTTPS, HTML and CSS and Firefox isn't breaking any of those with any upgrade. I also don't see banks releasing Firefox extensions.

    18. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      You know, I'm tending to agree with you now.

      Last 15 years i have been predominantly making my bread and butter from Open Source, and now cos of a change of location find myself as an IT manager in the Health industry. In the past i have always preferred Firefox and suggested to users that they use it. I have it deployed across the network here now but am finding that after version 3.6 a lot of health related sites and web applications no longer work with Firefox.

      So i have the choice to either stick at FF3.6 which i know works on the respective sites or use IE which works through all the versions and is manageable through AD.

      Im afraid its now coming to the time where Firefox is no longer the most suitable tool for the job.

    19. Re:Does Mozilla not read Slashdot? by theweatherelectric · · Score: 1

      I know zero out of dozens of people that like the direction firefox is going in.

      I know dozens out of dozens of people that like the direction firefox is going in. I've found the latest versions of Firefox to be faster with more capability than previous versions. It's why I use the new releases and not the old releases.

    20. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      The other issue is that Chrome doesn't tie compatibility to version numbers. When I update Chrome I don't get a box telling me it is disabling half my extensions/apps. For the most part, everything just works. So, the number is just a number.

      Mozilla's problem is that they assume extensions don't work after major version changes, which basically imposes arbitrary breakage. So, the number isn't just a number in their case.

      You have got it the wrong way around.

      It is not Firefox that assumes that extensions don't work after major version changes, it is the extensions themselves.

      Firefox itself and almost all extensions will in fact work perfectly well after major version changes, it is some older extensions which basically impose arbitrary breakage on themselves.

      There, FTFY.

    21. Re:Does Mozilla not read Slashdot? by Excelcia · · Score: 1

      If version numbers were just numbers it wouldn't matter. But version number inflating breaks plugins, and Mozilla is going "end-of-life" on previous versions much more quickly now. So instead of getting security patches for a year, you get them for a month. Now imagine you have a hundred, or a thousand PCs to support.

      The whole problem is that it's not a just a number. And that's what makes us upset.

    22. Re:Does Mozilla not read Slashdot? by ddegirmenci · · Score: 1

      Not everywhere. I don't know about Europe but the sibling poster has already mentioned banks in Asia using ActiveX and I can confirm the same thing in Turkey. Hell, my bank used to be OK with Chrome (which is no different to me from IE for most cases) until a year ago when they "updated" their online service. Now it only runs on IE.

    23. Re:Does Mozilla not read Slashdot? by jlebar · · Score: 1

      I can understand companies not being in touch with their customers, but does Mozilla not even read tech sites like Slashdot?

      The only thing which seems to happen more often than Firefox releases are posts on Slashdot complaining about them. :)

      Yes, many of us do read Slashdot. But believe it or not, we don't base all our decisions on what we see here.

    24. Re:Does Mozilla not read Slashdot? by Anonymous Coward · · Score: 0

      So where does Mozilla get the information they base their decisions on? Seems like your source it is very badly biased.

      Mozilla's home users are cumming in their shorts at the moment. But what happens when they can't access their favorite web sites which are - gasp - mostly made by the corporates you just pissed on to the point they won't support Firefox any more?!

  15. Re:Firefox has been fired. by Samantha+Wright · · Score: 3, Informative

    1. Memory leaks have been a major issue of recent Firefox development. Current FF 8 nightly builds use a tiny fraction of older versions, and they're extremely stable. This is accomplished by no longer caching previous pages (so if you go back, you'll have to reload from scratch.) I've got a cool 200 tabs open right now in a very old session and it's only using about 500 MB of RAM.

    2. The status bar can be restored with this extension. Addon compatibility is likely to be more stable in the foreseeable future since most of the major architectural changes were around the 3-to-4 transition.

    3. Firefox doesn't run on the iPad. Are you a troll, technically inexperienced, or in a state of reduced mental capacity?

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  16. Re:STOP by Larryish · · Score: 3, Interesting

    Everybody who still uses 3.6, raise your hand.

    *raises hand*

  17. Comments on the browser itself? by vlm · · Score: 5, Insightful

    So... 40 posts about how much better the support experience would be if they incremented it by 0.1 instead of 1.0, as if the bugs somehow know which digit was incremented. But, no comments about the actual browser? For example, have they finally reverted "tabs on top"?

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    1. Re:Comments on the browser itself? by Briareos · · Score: 5, Informative

      For example, have they finally reverted "tabs on top"?

      So right-clicking somewhere in the toolbars to bring up the toolbar context menu and unchecking "Tabs on top" (which I actually like a lot, thankyouverymuch) is too much to ask?

      --

      "I'm not anti-anything, I'm anti-everything, it fits better." - Sole

    2. Re:Comments on the browser itself? by Evan+Meakyl · · Score: 1

      Thanks for your comment, I wasn t aware that it is possible to disable this "feature"!!! (and never thought it would be possible this way!)

    3. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0, Flamebait

      For example, have they finally reverted "tabs on top"?

      You're a prime example of why Mozilla doesn't take any of this recent huff seriously. Your concerns are meaningless, negligible, and amount to nothing but white noise. You are bike-shedding in your own world. You act as though there isn't even a clearly and readily available GUI option to disable Tabs On Top.

      It'll be nice in a few more months when everyone has naturally gotten over their all-too-human completely irrational emotional response to change. Mozilla shouldn't fall for any of this bullshit in the meantime.

    4. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Have you ever used FF4+? Tabs on top is NOT the default.

    5. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      And this is exactly why Mozilla doesn't listen to the "browser expert" nerds on Slashdot! :P

    6. Re:Comments on the browser itself? by man_of_mr_e · · Score: 2

      It's people like you that are making so much noise. For example, when FF4 was released, everyone bitched that the dropdown menu was gone from the back and forward buttons. They wailed that there was no way to go back in the history more than one page at a time.

      Of course, that was entirely false. All they had to do was one of two things. Right click on the button and the history dropdown appears, or click and hold and it appears. It's like people have forgotten that they can actually poke around and figure things out for themselves. If it's not readily apparent, they assume it can't be done.

    7. Re:Comments on the browser itself? by visualight · · Score: 1

      Have you ever used FF4+?

      Nope. Too late.

      --
      Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
    8. Re:Comments on the browser itself? by Cyko_01 · · Score: 1

      it is also under the view > toolbars menu or the firefox > options menu depending on your configuration.

      P.S. I like it too

    9. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      We've been spoiled by _good_ UI design. Fancy that.

    10. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Because goodness knows that if the average user cannot find what they want to do, they will spend the time to poke around. You know, the alternative to calling their children or younger neighbor, making a complaint, taking it to a computer shop and being told its their RAM's fault and buying more or using some other software.

    11. Re:Comments on the browser itself? by jira · · Score: 1

      It's like people have forgotten that they can actually poke around and figure things out for themselves. If it's not readily apparent, they assume it can't be done.

      I think you got it wrong. The software should adjust to its users not the other way round. Even if you think that your users are lazy and not willing to invest few minutes of their time to learn the new great features you have for them then you should try to force yourself to listen to them. Because, well, otherwise they will just stop being interested in you at all. Well, in the end there will be an adjustment and Mozilla will have the sort of users it wants - somewhere around 5-10% market share would be my guess.

    12. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      If it's not readily apparent, they assume it can't be done.

      If it's not intuitive, it's poor UI design.

    13. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      I disagree. Good UI design is intuitive, sure. However, basic functionality needs to be obvious. More advanced functionality can require some learning curve. Going back multiple pages simply isn't something the majority of people start out doing. Even with a dropdown, they often don't even realize they can do it.

      I think it's perfectly acceptable that advanced features require knowledge, and not be in your face obvious.

    14. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      We're not talking about clueless people here. We're talking about slashdot users, and those in other forums for technical support. These are more advanced users, and those perfectly capable of digging around.

      As I said in another post, this is not basic functionality, it's more advanced and there's nothing wrong with more advanced functionality needing to have some knowledge to utilize.

    15. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      I wonder how well that translates to web sites. I thought the cardinal rule for web site UIs was to make navigation and layout absolutely clear at first glance, no gimmicks or stuff for people to "poke around and figure things out for themselves." Was saving the few pixels for the drop down menu cue really worth it? I don't think "requires poking around and figuring things out" is a good advertizing slogan or feature, especially for mainstream computer users.

    16. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      You can't make every feature in your face obvious. That clutters the UI, and makes it harder for users. You have to make more advanced features less obvious, or else it ruins the usability of the interface. Further, I don't consider right clicking on something to be all that un-obvious. We've been using context menus for almost 20 years now.

    17. Re:Comments on the browser itself? by FooBarWidget · · Score: 1

      But the question is which users? If a UI changes makes things better or easier for 80% of the users but pisses off 20% of the users, then I'd say go for it. The back button history dropdown makes the UI look less cluttered and saves screen real-estate. Most average users never use the dropdown. It's an overall win. Only the vocal 5% minority chooses to scream death instead of rightclicking and moving on.

    18. Re:Comments on the browser itself? by Blaskowicz · · Score: 1

      as it is the feature is totally undiscoverable, and is backed by no user experience - I've never ever used a context menu on a browing button, from windows 3.1 to nowadays. I wouldn't know of the feature if it were'nt for you pointing it out in a slashdot comment, thanskfully I tend to rely on tabs rather than back/forward. There's no excuse for an invisible and totally non standard UI control, as even advanced users can't know it is there.

    19. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      Well, IE and Chrome both do it the same way, and have for quite some time. So in that sense, Firefox is just bringing parity.

    20. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      We've been using context menus for almost 20 years now.

      That's correct and the virus writers love you for clicking on everything on the web page with both buttons. While you're at it be sure to enable all keyboard shortcuts.
      The stable version is probably still 3.6.17

    21. Re:Comments on the browser itself? by 0123456 · · Score: 1

      But the question is which users? If a UI changes makes things better or easier for 80% of the users but pisses off 20% of the users, then I'd say go for it.

      If those 20% of users are the dedicated ones who tell their friends 'why are you still using IE? You should be using Firefox, it's way better' then pissing them off means you're fscked.

      The back button history dropdown makes the UI look less cluttered and saves screen real-estate.

      Where did this 'clutter' bullshit come from anyway? How many people have you heard say 'well, I'd love to use Firefox, but it's just too cluttered?' Sure on my netbook I don't have a lot of screen space, but most of the time I'm using Firefox on a screen that has plenty; there's precisely zero reason to want to run software that looks like it was designed for a mobile phone. The primary impact of 'decluttering' the interface is to force me to click the mouse six times to do something that used to require clicking ones. Do you really think I won't be pissed off by that? Do you think I'll randomly click around the UI or explore about:config in the hope that you might have hidden an option to give me back the old interface that worked and not post about how retarded the developers are for removing it in the first place?

      Major FOSS developers seem to have gone insane in the last year, abandoning the markets they have in the hope of gaining markets they don't. It's retarded.

    22. Re:Comments on the browser itself? by 0123456 · · Score: 1

      It'll be nice in a few more months when everyone has naturally gotten over their all-too-human completely irrational emotional response to change. Mozilla shouldn't fall for any of this bullshit in the meantime.

      In two years Firefox market share will be 20% and they'll be wondering where all their users went.

    23. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      Who said anything about a web page? What a stupid argument.

    24. Re:Comments on the browser itself? by Jah-Wren+Ryel · · Score: 1

      as it is the feature is totally undiscoverable,

      All it takes is to normal-click and the pause for like a second while you hold the mouse button down which isn't such a rare thing for many users to do, especially the older ones with less pliable minds who sometimes have to take a second or two to figure out what they are doing. It seems eminently discoverable to me, because, well, that's how I discovered it.

      --
      When information is power, privacy is freedom.
    25. Re:Comments on the browser itself? by imunfair · · Score: 1

      Well, I do agree that he should have been able to Google for a solution. That said, I'm rather tired of looking up workarounds when they screw with features in each version. This is especially true when I have to re-patch all the 'problems' on every new release. With Firefox it's at the point where the only time I actually upgrade is when I reinstall my OS. I would have switched to Chrome ages ago if they had the plugin support for features like NoScript, that's how obnoxious I feel Firefox default settings have become.

    26. Re:Comments on the browser itself? by kangsterizer · · Score: 1

      Its hype to bash Firefox and acclaim Chrome - even if what people bash Firefox for is what Chrome is doing.
      The actual changes and features, nobody cares!

      The sad state of the current browser war and so many other things. What matters lately is what will sound cool/bad, what will give you senseless forum arguments.
      Not the reality. We've became _that_ superficial.

    27. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      I bet you were one of the developers of Milon’s Secret Castle, right?

    28. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      No, it's the fact Mozilla thinks numbering it this way DOES something special. It removes faith from the project when they believe such idiocy.

    29. Re:Comments on the browser itself? by Billly+Gates · · Score: 1

      Chrome supports XSS protection which was one of the main arguments for using noscript. Chrome is well patched against most javascript exploits that are local these days and a good antivirus product will catch any that get through.

      Chrome is coming up with its own version of noscript in a future release.

      It is pretty safe now to leave Firefox. Personally, I can't stand noscript as it bleeps like the UAC controls in Vista each time I go to a page I have never been before and that drives me nuts.

    30. Re:Comments on the browser itself? by FooBarWidget · · Score: 1

      If those 20% of users are the dedicated ones who tell their friends 'why are you still using IE? You should be using Firefox, it's way better' then pissing them off means you're fscked.

      The 1% Linux users are extremely hardcore about the command line and tell their friends to use Linux. Has optimizing the UI for those 1% helped Linux gain more market share?

      Where did this 'clutter' bullshit come from anyway? [...] Major FOSS developers seem to have gone insane in the last year, abandoning the markets they have in the hope of gaining markets they don't. It's retarded.

      I wonder how much of your opinion would hold when under scrutiny of a professional usability expert.

    31. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      So they fucked with the default method that worked for no damn reason.

      If something is gone, why would you assume it's just hidden.

    32. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      you can customize pretty much everything in FF.. though some things require a bit of work (ie, editing CSS files as opposed to choosing menu options)

    33. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      a professional usability expert.

      Everyone is a professional usability expert, for themselves at least.

    34. Re:Comments on the browser itself? by voltboyee · · Score: 1

      Just installed it. All of my addons are working (Lastpass, XMarks, Adblock Plus, Download Statusbar, Stumbleupon, Flagfox). Oh I saw that it broke Java Console 6.0.26 but I dont come across too many Java applet sites lately anyway. Not sure why they decided to go on a version number rampage but I have never had a problem with Firefox.

    35. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Does good software hide useful features from the user just to have a more 'streamlined' interface?

      What's the point in such features being there if a good 90% of the userbase who want to use them no longer think they are, and new users aren't likely to discover them? That's BAD interface design, and that's why people are making so much 'noise'

      I post this from Firefox, which I'm now ONLY using because of NoScript, there are no longer

    36. Re:Comments on the browser itself? by Excelcia · · Score: 1

      Well, I'll jump in and say with several polls showing that >80% of users who know about the way to disable tabs on top doing just that, my question is why make the majority of your users jump through the hoop?

    37. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      And it's people like you who forget that other people don't want to dig around in their browser. It is worse when the UI designer expects the user to do some UI action that has no visible cues.

      "All they had to do was one of two things." neither of which are apparent at all.

      The browser isn't Nethack.

    38. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Firefox has tabs on top? Seems I haven't clicked the Firefox icon within the last 3 days to notice the change...

    39. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Yep, that's one of the good things about Firefox, and one of the only reasons I use it instead of, say, Chrome: it's very customizable. Even without going into about:config, you can change way, way more things about it.

    40. Re:Comments on the browser itself? by Pascal+Sartoretti · · Score: 1

      For example, have they finally reverted "tabs on top"?

      I hated it at first also. But give it a try. And watch the video here if you want to know why it is better.

    41. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      For example, have they finally reverted "tabs on top"?

      So right-clicking somewhere in the toolbars to bring up the toolbar context menu and unchecking "Tabs on top" (which I actually like a lot, thankyouverymuch) is too much to ask?

      So when I am upgrading from a previous version of FF, defaulting to the old behavior or specifically asking if I want to change it is too much to ask?

    42. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Well, right clicking a button is not a normal action. We right click text all the time, but buttons normally (and should) have one function. An essential function should not be hidden like this. It was a stupid idea. How the hell was it intuitive? And it says 12 pixels?

    43. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Because features are rarely removed from programs, being accessible in a different way is more likely than completely removed.

    44. Re:Comments on the browser itself? by AmIAnAi · · Score: 1

      Maybe I missed the big whooshing sound as your comment went over my head, but I suspect there wasn't one. If "everyone bitched" then the developers got it wrong. This isn't some obscure utility that is put out by a tiny dev team, this is a workhorse tool and people expect to be able to update and continue working as before - nothing broken, nothing missing and certainly no requirement to go reading through documentation to get back to where they were 5 minutes earlier. If the Firefox dev team were saying 'here's something we wrote for ourselves, use it if you like' then sure, they're free to make whatever changes they like, but when they start evangelising and actively courting users for their product they need to stop listening to their egos and listen to the end users.

      --
      Any sufficiently advanced bug is indistinguishable from a feature.
    45. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      The 1% Linux users are extremely hardcore about the command line and tell their friends to use Linux. Has optimizing the UI for those 1% helped Linux gain more market share?

      I (and many others) found an even better solution.

      I used to argue they should switch to Linux, because it has a lot fewer problems, and is easier to support remotely (no, enabling Remote Desktop was not an option on Windows 98).

      Now, I'm just: "Oh, you're using Windows. Sorry, I have no idea about that problem, I use Linux. Better ask someone who uses Windows".

      Even easier than supporting Linux.

    46. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      Actually? Yes. It really is.

      It wouldn't be too much if doing that was what it took to ENABLE tabs on top, but changing an existing UI for NO FUCKING GOOD GODDAMN REASON and leaving it up to the user to figure out (not everyone is technically inclined) is stupid and shows a lack of concern for the userbase.

    47. Re:Comments on the browser itself? by webheaded · · Score: 1

      Apparently. I cannot believe how much complaining I see on here about every single graphical change. Almost all of them can be reverted by simply changing a few options. Takes a few minutes and hell, you usually don't even have your settings changed if you upgrade the browser. I had to revert stuff to defaults for Firefox 4 a few times to get it to look the new way (which I actually like...I guess I'm weird). Defaults are defaults. We're nerds here...who the hell ever uses ALL of the defaults here?

      For a bunch of technology enthusiasts some of you really hate change which really just perplexes me. All I ever seem to see here is complaining about everything. It's exhausting after a while.

      --
      "Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
    48. Re:Comments on the browser itself? by Whorhay · · Score: 1

      Really? I'm using IE7 and there is no special context menu for the back and forward buttons. There is however a small dropdown arrow button next to them which gets a lot of use.

    49. Re:Comments on the browser itself? by man_of_mr_e · · Score: 1

      IE7 is almost 5 years old. IE9 no longer has the drop down.

    50. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      I think unchecking the box "Audio feedback when scripts are blocked" was one of the first things I did after installing noscript. Having to whitelist javascript on specific sites just seems like a stronger security model than "oh I hope my antivirus vendor manages to catch any new exploits before they affect me".

    51. Re:Comments on the browser itself? by Anonymous Coward · · Score: 0

      I remember watching that video and I thought "boy, is that a dumb way of thinking about it." Their schema doesn't match mine (which is that the browser is a program that has certain, unchanging elements - these elements are separate from a given page and I think of the title of the page as the tabs title (leaving aside the window title sharing it)). Thus, separating the title from the content is disjointed - not to mention that fact that I almost never mouse to the location bar, back/forward bar, search box, etc but just use keyboard shortcuts so having these elements closer to the content does me no good.

    52. Re:Comments on the browser itself? by SydShamino · · Score: 1

      I searched for this story and dug through these comments to figure out how to put the tabs back where they belong, because I couldn't find it in the Options menu. Is not hiding things in pointer-location-specific context menus too much to ask? Why isn't in a menu when you right click on the tabs?

      --
      It doesn't hurt to be nice.
  18. Re:Firefox has been fired. by iggymanz · · Score: 1

    There is a great fork, Seamonkey. Runs on Windows, GNU/Linux, Mac OSX, OpenBSD, FreeBSD, NetBSD, and DragonFly (for the *BSD use their ports collection) . The latest version 2.2 came out 07 July 2011. Runs all the firefox addons I use, though you'd have to check the ones you like.

  19. Re:STOP by houghi · · Score: 2

    Version number doesn't matter

    But this one goes to 6.

    --
    Don't fight for your country, if your country does not fight for you.
  20. Re:STOP by armanox · · Score: 1

    I hated 3.x. I stayed on 2.x until Chrome was released. Firefox 4+ has brought me an interface that I can stand again.

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  21. Re:STOP by Anonymous Coward · · Score: 0

    Go to hell Mozilla

    Version number doesn't matter, just fix whats broken and stop messing with the interface THAT WORKS.

    The old interface is cluttered and wasteful. Most people will say that isn't considered "working". If you want the old interface, make a few checkmarks under View and you're there. It's shocking that people on a site that's supposed to be for "nerds" do not know how to use GUI menus.

  22. Don't feed the troll by Anonymous Coward · · Score: 0

    Obviously

  23. If there was a "This title is misleading" button.. by Anonymous Coward · · Score: 0

    ... I would click it for almost every single Slashdot story. Firefox 6 has NOT been released. When Mozilla releases it, they will change the Firefox homepage. Being software developers, they know how to change their websites.

    kthxbye

  24. 10.7 by Anonymous Coward · · Score: 0

    Did you try 10.7? Their interface is becoming inconsistent as well.

  25. So I guess Google toolbar is done then? by taxman_10m · · Score: 1

    Or how many releases have to go by before it is supported again?

    1. Re:So I guess Google toolbar is done then? by PalmAddict · · Score: 1

      It's not coming back. Sorry. Toolbar was done when 5.0 came out: http://www.google.com/support/toolbar/bin/answer.py?answer=1342452&topic=15356

    2. Re:So I guess Google toolbar is done then? by kbrosnan · · Score: 1

      Mozilla has no control over Google's toolbar team. If they don't want to support a browser there is nothing Mozilla can do. The Google toolbar is closed source binary extension.

      --
      These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
    3. Re:So I guess Google toolbar is done then? by aitan · · Score: 1

      Google said that they are dropping it.
      If you want to blame someone for not being updated, blame Google

    4. Re:So I guess Google toolbar is done then? by Billly+Gates · · Score: 1

      Google said they will only support the latest 2 releases of a major browser.

      However in practice I believe this meant IE. Google would do the web a huge service by getting offices off of these 10 year old buggy browsers. IE 6 & IE 7 are majorly crappy, backwards, and far behind the times compared to Firefox 3.6. I see no reason why watching a video on youtube or using the Google Earth Plugin would not work well on Firefox 3.6. I no longer have Firefox 3.6 so I wonder if anyone can confirm if Google displays a warning message or not? My guess is no.

      IE 8 in comparison is more like a real browser at about Firefox 2.x ish in terms of features and no real hacks and support headaches so you can do thinks like use Google Maps with it. I can see why Google would want to support that as the earlier browser and going backwards no further than that.

  26. Re:STOP by Cyko_01 · · Score: 1

    that is exactly what they are doing. 4.0 was the last major UI change and that is part of the reason it took so long to release it. There are no major UI changes until at least fx8 (to help add-on creators cope with the new rapid release schedule), and they are getting fixes out to the user faster then before. YOU are the one who is fixating on the version numbers, not them. The major version number (the first digit) does not symbolize major changes, but a stable release - which this is - only with fewer changes then fx2/3/4.

  27. Re:Firefox has been fired. by linebackn · · Score: 1

    I don't think this should have been modded down, it sounds like a Firefox experience that is sadly going to become more common for average users.

    Don't know if anybody even noticed, but Mozilla shut down Spreadfirefox.com (now it just redirects to a page on Mozilla's main site) just before they released Firefox 4. Admittedly, the community had already gone down the toilet and the site was mostly just collecting spam.

    (also the poster said he started using an iPad with Safari, not that he had been using Firefox on it)

  28. Re:STOP by gfody · · Score: 1

    The thing I like about firefox is that you can completely rearrange the interface. For me every version has looked the same.. I don't really care what they do with the default settings.

    --

    bite my glorious golden ass.
  29. Re:STOP by subanark · · Score: 1

    Using Cent OS 6 at work. I'll just wait until they include a new version of firefox in their standard distro before I upgrade.

  30. "Supposed to"? by Anonymous Coward · · Score: 0

    No. They're encouraged to, that's quite different. The stable API sounds like the way to go if you want to provide a good end user experience for add-ons, and it makes the most sense. The bleeding edge API is for testing.

  31. Re:STOP by visualight · · Score: 1

    3.6 is the last one me or anyone I know will ever use. They've jumped the shark.

    --
    Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
  32. Re:STOP by Osgeld · · Score: 1

    can you do that in 4? I havent tried to

  33. Re:STOP by visualight · · Score: 1

    The old interface is cluttered and wasteful. Most people will say that isn't considered "working". If you want the old interface, make a few checkmarks under View and you're there. It's shocking that people on a site that's supposed to be for "nerds" do not know how to use GUI menus.

    It's shocking just how out of touch Mozilla has become. This whole "clutter" argument from self titled "UI experts" is just tiresome now.

    --
    Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
  34. Fx has bigger problems than its versioning policy by Anonymous Coward · · Score: 0

    Fx displays mediocre performance for me with only 3 plugins installed. It has been doing so for a long time. I noticed a clear improvement in speed with v4 but I still get, out of the blue, constant whole window freezes for 10-30s - during which one core of my CPU spikes to 100% - especially if I have a few pages with Flash opened. I tried many tweaks to get around it but sooner or later the problem comes back.

    I suspect that this is, to a large extent, Google's fault because the freezes appear especially on GMail, G+, Reader and Youtube. They must be pushing the envelope with the complexity of these sites, Fx seems to be unable to handle it and Google doesn't care anymore since they successfully positioned their own browser as the paragon of speed. Then again, I do use Google's site predominantly so maybe I would see the problem elsewhere.

    I'm worried that this both perceived and factual performance problem will seriously hurt Fx. I've been using Fx and its ancestors for more than 10 years and I've never been so close to abandoning it. If I could have "Search With" for Chrome, I'm pretty sure I would start using it as my primary browser.

  35. does it crash less than FF 5? by Anonymous Coward · · Score: 0

    FF 5 added some good features, but it crashed more than any other version of Firefox.

  36. Re:STOP by 6350' · · Score: 1

    *raises hand* It was the UI changes in 4 and on that kinda turned me off.

  37. Re:STOP by 6350' · · Score: 1

    How strongly is that the case in FF6? I'm still using 3.6.

  38. Re:STOP by Darkness404 · · Score: 1

    Exactly, and you can still customize your browser. The fact that you can't even change basic history settings in Chrome, let alone all the about:config tweaks in Firefox, has made me stay loyal to Firefox. If Chrome actually let you have decent customization and decent extensions, I might switch. But the complete lack of customization has stopped me from using Chrome.

    --
    Taxation is legalized theft, no more, no less.
  39. Re:STOP by Darkness404 · · Score: 1

    Most of us don't want change for the sake of change. Change for the sake of change is -never- a good thing and just pisses off users. And it seems like everything is changing for the sake of change such as GNOME, Facebook, and now Firefox. At least with Firefox the UI is customizable enough I don't have to deal with the hideous new UI which you can't change really fore GNOME 3 or Facebook.

    --
    Taxation is legalized theft, no more, no less.
  40. Beta version by Woogiemonger · · Score: 1

    Upon installing, it says "Welcome to Firefox Beta". In "About Firefox", it doesn't mention anything about beta though. So I'm not exactly sure if this is beta. If it is beta, it's weird it's available by a URL that has no mention of "beta", no?

    1. Re:Beta version by surveyork · · Score: 1

      The first run page says "Beta" because it hasn't been officially released yet. Firefox 6 is officially still in beta and won't be publicly released until August 16.

      --
      2019 is going to be the year of Linux on the desktop.
  41. A way to determine beforehand? by Rhapsody+Scarlet · · Score: 1

    Talking of extensions (I believe the above poster is actually referring to extensions rather than plugins, plugins generally don't break with new versions), is there any easy way to determine whether or not my current set of extensions are compatible with a given version? I'm on Debian so all of my updates come through my package manager, and the 'easiest' way at the moment seems to be cross-referencing each extension (all twenty-six of them) with Firefox Add-ons, which tedious in the extreme.

    Is there just some tool which can scan through my extensions and report back on which aren't marked as compatible with 6.0 or above?

    1. Re:A way to determine beforehand? by simcop2387 · · Score: 1

      Off hand i can't think of a tool to do this. However, you could always grab the build from the mozilla servers and run it from your home directory. this would check if your plugins are compatible. of course you should back up ~/.mozilla before you do this. I haven't had that break anything since firefox 2, but it is always possible.

    2. Re:A way to determine beforehand? by Anonymous+Psychopath · · Score: 2

      Is there just some tool which can scan through my extensions and report back on which aren't marked as compatible with 6.0 or above?

      Yes, Is It Compatible? does this.

      --

      Eagles may soar, but weasels don't get sucked into jet engines.

  42. Re:STOP by Culture20 · · Score: 1

    The old interface is cluttered and wasteful.

    When I needed the wasteful old interface to stop cluttering, I could hit F11 for a full screen view. Does F11 bring back the extremely useful clutter in FF4/5/6?

  43. Firefox Upgrade by Anonymous Coward · · Score: 0

    Have they fixed the freaking memory leaks issue yet? No? Hrmph, no thanks, Mozilla. FF5 leaks bad enough as it is, I'll stay with it rather than move up. If you want people to be interested in upgrading to your newest version, try fixing the bugs instead of just adding feature bloat or trying to make your browser score higher than Chrome on some benchmark.

  44. 64bit by Anonymous Coward · · Score: 0

    What is a 64bit version going to be made available?

    1. Re:64bit by Anonymous Coward · · Score: 0

      When you install Linux?

  45. It's still beta and download folder says so! by Anonymous Coward · · Score: 0

    From the download folder:

    We aren't quite finished qualifying Firefox 6 yet. You should check out the latest Beta.

    From the Welcome page when you install the executable at the link provided:

    You are now running Firefox Beta

  46. index.html by macraig · · Score: 1

    Thanks for your interest in Firefox 6

    We aren't quite finished qualifying Firefox 6 yet. You should check out the latest Beta.

    When we're all done with Firefox 6 it will show up on Firefox.com.

  47. Spiraling out of control by Darth_brooks · · Score: 1

    Firefox seems to be spiraling out of control in the name of its own mission statement.

    The reaction to the numbering scheme has been strongly negative. The enterprise mailing list was launched ostensibly in an effort to "communicate" with enterprise users and see what Mozilla could do to bridge the gap between the needs of enterprise and the state of firefox. The community has laid out the two simple concepts that have had us in enterprise either most up in arms or would most like to see. Those requests have fallen on ears that are either willfully sealed shut, or passively hoping that the status quo is gonna be ok. It's been a handful of the Mozilla team doing little more than trying to find new and creative ways to say "Enterprise doesn't fit our mission statement, so you can all just fork off" without coming out and saying it. We've said what we need, and the response has been a deafening "That's nice, we're gonna keep doing what we're doing."

    I can't see a good future for Firefox at this point. 3.6 is starting to look more and more like Netscape 4.7 to me. The highwater mark before things began rolling back. They could have changed the world, but they seem hell bent and whiskey bound on sitting in their sandbox.

    --
    There are some people that if they don't know, you can't tell 'em.
    1. Re:Spiraling out of control by Anonymous Coward · · Score: 1

      The community has laid out the two simple concepts that have had us in enterprise either most up in arms or would most like to see. Those requests have fallen on ears that are either willfully sealed shut, or passively hoping that the status quo is gonna be ok. It's been a handful of the Mozilla team doing little more than trying to find new and creative ways to say "Enterprise doesn't fit our mission statement, so you can all just fork off" without coming out and saying it. We've said what we need, and the response has been a deafening "That's nice, we're gonna keep doing what we're doing."

      This reminds me of the time Mozilla dropped MNG image support (Bug 18574) because it added 50k to the size of the binary. The developer community addressed that issue and other excuses that the Mozilla team came up with to justify removing it. Asa finally said they would refuse to restore MNG support because so many users had been asking for it. Long after most users have forgotten what MNG was, and after Mozilla's install base grew exponentially, MNG support still has the most votes of any item in the Mozilla bug tracker.

    2. Re:Spiraling out of control by surveyork · · Score: 1

      Well, when Mozilla devs can be pretty stubborn when they say they won't fix a bug. Take the case of "Paste and Go", for instance. Or the case of the Acid3 Test. They said they won't fix the remaining bugs on principle. Yes, Acid3 is somehow arbitrary, but it would be good for PR, and implementing SVG fonts would be good for open standards and web developers worldwide.

      --
      2019 is going to be the year of Linux on the desktop.
  48. Rapid Release - a Tradeoff by kripkenstein · · Score: 4, Informative

    I can understand companies not being in touch with their customers, but does Mozilla not even read tech sites like Slashdot? Every story about Firefox lately is filled with exactly how negatively people feel about this version number fiasco.

    Chrome was able to get away with bumping version numbers because it was a very new product and nobody was depending on it yet. Even though they removed the "beta" tag surprisingly early on (for a Google product), I think many people STILL consider Chome as "beta".

    On the other hand large corporate type applications were just beginning to support Firefox and depended on long term support of major versions. Well, that has just been stomped in the face. Sadly, from a corporate stand point the only browser that really seems stable, viable, and "corporate friendly" now is IE.

    Hi, I'm a Firefox dev. Yes, we read Slashdot :)

    There is a big tradeoff here, with downsides both ways. You correctly point out that some people are having problems with the new fast release schedule. That's a fact, and we are doing all we can, but the problems are hard (addons, enterprise users, etc.).

    On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users. For example, FF8 will have much better memory usage than Firefox 4. Releasing new versions quickly lets users get that benefit quicker - fewer users will have memory problems because we ship the fixes faster. As another example, when IE9 and FF4 came out, at roughly the same time, they had comparable performance on some canvas benchmarks (in which they outperformed all other browsers due to their being the only browsers to use Direct2D). Meanwhile Firefox has released twice (counting FF6 on next Tuesday), and as a consequence, Firefox users have better performance than IE users, simply because IE users are still on IE9 while Firefox users can run FF5 and FF6 which include a lot more performance improvements that were committed after FF4.

    Another major issue is new web standards. For standards to evolve quickly, browsers need to ship new versions with new implementations of those standards. Firefox and Chrome are now leading that, by releasing every 6 weeks. As one example, both support the new (safe) version of web sockets. That pushes the web forward, letting developers use it quicker, and eventually let all of us benefit from those new features. Chrome began this push, and I think Google was right to do it, and Firefox is joining that.

    Is the new release schedule perfect? Of course not. It has problems for both browsers doing it, Chrome and Firefox. Both are probably not seen very favorably among enterprise users. And Firefox has some additional challenges, what with transitioning a previous release schedule to this one. But still, both Chrome and Firefox feel it is worthwhile. So again, I realize that there are problems. But overall I think the fast release schedule of Chrome and Firefox is a good thing.

    1. Re:Rapid Release - a Tradeoff by springbox · · Score: 2

      I don't think anyone really minds if new versions are released often, but the issue of add-ons breaking because of the chosen versioning scheme is probably the largest annoyance. You can still release often without changing the major version number, at least until you can convince add-on developers to use the new SDK.

    2. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Is there any reason these same rapid releases could not have been called 4.1, 4.2, 4.3, and 4.4, or if the differences are major enough, FF5 Milestone 1, Milestone 2, Milestone 3, and Milestone 4 (beta)?

    3. Re:Rapid Release - a Tradeoff by Culture20 · · Score: 2

      On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users. For example, FF8 will have much better memory usage than Firefox 4.

      Then name "FF8" FF4.5 and be done with it. Are we really to believe that the better mallocs are tied to the new UI features?

    4. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 4, Interesting

      The problem is that Chrome and Firefox 6-week updates can and do change functionality and break internal APIs. Regardless of whether those browsers raise the major version number, addons can break.

      Chrome deals with this by having a limited addon API that does remain stable. This limits what addons you can write for Chrome, but it does make 80% of addons possible and with less upgrade hassle.

      Firefox is moving to allow that approach with the jetpack SDK. However addons that don't use that SDK are relying on internal Firefox APIs, and the power and flexibility that that gives does mean they are at risk for breaking. Note that Mozilla's addons website will automatically check the code of addons hosted on it for actual API incompatibilities, and auto-mark as compatible addons that are not at risk. So a lot of addons 'just work' because of that. But still, some addons do rely on changing APIs, and some addons are not hosted on addons.mozilla.org, so the authors need to manually update them.

    5. Re:Rapid Release - a Tradeoff by kangsterizer · · Score: 1

      What's important is to have LTS release for the enterprise.
      Like FF4, FF8 could be LTS. LTS means security fixes. Also have MSI packages for those lazy admins that can't create one themselves.
      That's mostly all that is needed and just need ONE guy at Mozilla, not even full time, to please the internet and enterprise.

    6. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 2

      No reason, but it wouldn't solve much either. Whether we called 5 something like 4.1, doesn't affect the fact that 5/4.1 does have some incompatibilities with 4.0 (new APIs, deprecated APIs, bugfixes to existing APIs, etc.). So calling it 4.1 would not have solved the real issue, and would have potentially made things worse by making some addons think they would work when they won't (but it would have made some addons work that currently don't, that's true).

      Personally I am not a fan of the major number bump every 6 weeks. Just because I am used to other ways of numbering releases. But, I do understand the reasoning for it: To be consistent with Chrome, which already does that, and to be clear that these 6-week updates do change APIs and functionality, which they do (I assume that's why Chrome started with it in the first place).

    7. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 2

      There are downsides to naming it FF8 and downsides to naming it FF4.5. For example, calling it FF4.5 might lead people to assume there are no API changes (point releases often mean just that). But Chrome and Firefox do change APIs and functionality with their 6-week updates. So it is technically more correct for both of those browsers to bump the major version number each time - even though it does feel odd, and I admit it annoys me personally (but I am slowly getting used to it).

      I am not sure what you mean by memory stuff being tied to new UI features? Generally those things are independent, yeah - has someone said otherwise?

    8. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 2, Interesting

      What's important is to have LTS release for the enterprise. Like FF4, FF8 could be LTS. LTS means security fixes. Also have MSI packages for those lazy admins that can't create one themselves. That's mostly all that is needed and just need ONE guy at Mozilla, not even full time, to please the internet and enterprise.

      I agree 100% that Firefox should have an LTS release. Also that we need MSI packages. However, I want to clarify that it would be a lot more than one person can do: It is a lot of work to maintain a stable release, you need lots of QA for every update and for every single OS it will run on. You also need support from other parts of the organization, from build infrastructure to technical documentation. Overall it is a significant effort to really do it seriously and properly.

      I am less sure how hard it is to make MSI packages, I don't run Windows and never used that stuff myself.

    9. Re:Rapid Release - a Tradeoff by akaariai · · Score: 1

      I just installed Firefox nightly (8.0a1, 2011-08-14). Adblock Plus, NoScript and HTTPS everywhere are working, Ubuntu Extension is not. Ubuntu extension is also disable as an auto-installed extension.

      The memory consumption seems to be under control also, but too early to say. Currently the memory usage is 110-120Mb with one hour of use time and about 10 tabs open. I hope it is not 500Mb after a weeks use.

    10. Re:Rapid Release - a Tradeoff by ThePhilips · · Score: 1

      On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users.

      And how is all the nifty features are related to fsckups of the user interface? Right...

      Why can't you accumulate features and make a major release, say once a year? Many people are boasting here constantly that they are using alphas/betas, like before they have used NBs. There was never problem of getting latest and greatest FireFox in hands of users - except for slightly fscked up handling of profiles. Which you surely could have fixed instead.

      As one example, both support the new (safe) version of web sockets.

      You operate on false presumption that users are after latest and greatest features - the features which are totally invisible to them. They are not.

      How a user who mostly visits Facebook and Wikipedia and probably corporate Intranet profits from WebSockets? (Or the WebSockets had UI fsckup as a prerequisite?)

      [...] Chrome and Firefox. Both are probably not seen very favorably among enterprise users.

      No, simply "unsupported," what equals "use at your own risk; if stuff breaks royally - you're on your own." We recommend IE. There were plans to certify FireFox 3, but it became outdated in mean time (even security updates are broken now; we had to download 3.6.19 manually). With new release strategy it is simply impossible: we can't certify all versions of Fx as there are too many of them; we can't guarantee that stuff works in future versions (and customers must upgrade obviously to receiving security updates).

      But overall I think the fast release schedule of Chrome and Firefox is a good thing.

      You totally make no sense. You mix lots of technical and political issues together (akin to religion or corporate brainwashing) thus it is nearly impossible to see any logic in what you say. Frankly, I doubt there is any.

      --
      All hope abandon ye who enter here.
    11. Re:Rapid Release - a Tradeoff by linebackn · · Score: 2

      Thanks for your response. There certainly are plenty of people out there who demand the absolute latest and greatest, and demand it yesterday. You are certainly making these people very happy right now.

      But I believe you have seriously underestimated the impact of alienating the needs of your more technical, corporate, enterprise users and developers.

      As evidenced by the responses on Slashdot, many are finding it more difficult if not impossible to fully support a rapidly changing target. This means more internal applications will potentially now not support Firefox. Some internal applications may eventually become external applications. And such development views may spill over to existing sites and applications. Which in the long term means more IE-only web sites for Firefox users. On top of that corporate desktops are less likely to adopt Firefox, making it more likely that their employees may want or need to use IE at home.

      Although in the past Mozilla has not embraced the enterprise, its development efforts were not contrary to business needs, so it was making some headway.

      I strongly suggest that Mozilla developers take a visit to some stuffy corporate or government offices to see what their IT is like there. See how important contracts, long term support, politics, PR, and ass covering really are. Any place that uses Oracle software would be a good bet. :)

      There is never any one good answer to any given problem and I only wish I had a magic answer that would make even 99.90% of the people happy. (The only thing that comes to mind is a designated LTS version like what Ubuntu does, but Mozilla already has to worry about nightlys and betas). At any rate, it would be nice to see at least some official public response from Mozilla.org on this matter.

    12. Re:Rapid Release - a Tradeoff by kangsterizer · · Score: 1

      tenfour firefox seems to do well with little resources
      i dont think a LTS needs such large resources. maybe to have the LTS process in place yes, but thats a one time change.
      Anyhow, that kind of should be considered with importance, such bad press for FF makes a browser go down quickly.

    13. Re:Rapid Release - a Tradeoff by Pigeon451 · · Score: 1

      Thanks for these comments. I was unaware of why Firefox was moving to a faster release schedule, I've never heard a reason why! If it weren't for the addons, I would have switched browsers by now, but now I can be more patient. You may want to suggest to the team publishing an in-depth article explaining WHY Firefox has moved to a rapid release schedule, it may calm a lot of annoyed users.

    14. Re:Rapid Release - a Tradeoff by WoOS · · Score: 1

      I think the question is more on why Firefox all of a sudden needs constant API breakage.

      Picture yourself working on a software with a multi-million (probably tens of million) user base. Lots of external developers depending on the API (you proudly presented years ago). Your new boss comes in saying: "Hey guys, I heard about this bazar vs. Cathedral thing and the spiral software engineering model. Let's go to a monthly release schedule. All APIs are unfrozen. And get some UI designers. I want a new look in every version until we find the ultimate one."
      Do you
      a) Say "Yes boss. Will be done immediatly"
      b) Propose a fork to do all the explorative work and, once it stabilizes in a year or so, convince people to move over.

      It seems Firefox choose a) thinking it saves them the "winning over" after a year but which will actually loose a lot of people in that time or have people stop caring about updates.

      BTW, since Firefox didn't branch, a lot of people (including me on all non-security relevant systems) seemingly did it on their own as the still large share of 3.6 Firefox users show.

    15. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Kripkeinstein, please taking advantage of the fast release, look at this bug:

      http://support.mozilla.com/en-US/questions/810972

      http://support.mozilla.com/en-US/questions/795456

      I am still using firefox because of the noscript plugin.

    16. Re:Rapid Release - a Tradeoff by syousef · · Score: 0

      Hi, I'm a Firefox dev. Yes, we read Slashdot :)

      Normally, I'm very reluctant to be negative about anything that requires a lot of effort and is offered for free. But I am seriously tempted to just abuse ALL Firefox developers. The arrogance means you deserve to have your product die, and the way you're going it certainly will. The main reason I and most users make Firefox their usual browser is the wonderful extensions. But you keep breaking them with each release, and you are taking a sane interface and adding idiotic mimicry of horrible web 2.0-isms. The awesomebar is not and never will be awesome. Searching through and displaying my bookmarks whenever I search makes me uncomfortable using the browser with anyone looking (and no, I don't have any porn bookmarks, I just don't like advertising). I now need extensions just to undo the stupidity. You guys have collectively lost the plot. I'm past the point of reasoning with you and I now just wish Firefox would hurry the fuck up and die already so something else less SHIT can take over. In the meantime I'm writing this on Firefox 3.6, and I normally like to keep up with software.

      There is a big tradeoff here, with downsides both ways. You correctly point out that some people are having problems with the new fast release schedule. That's a fact, and we are doing all we can, but the problems are hard (addons, enterprise users, etc.).

      SOME people? SOME? Are you dense. READ the fucking comments.

      On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users. For example, FF8 will have much better memory usage than Firefox 4. Releasing new versions quickly lets users get that benefit quicker - fewer users will have memory problems because we ship the fixes faster.

      STOP with the bullshit!!!! Seriously! Just cut it the fuck out. You do NOT need to screw up the version numbers and increment by 1.0 each time to release new features and bug fixes. That is just BULLSHIT. You guys have been promising to fix memory issues and leaks for years now. Stop drinking the fucking coolaid.

      --
      These posts express my own personal views, not those of my employer
    17. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 3, Interesting

      I'm sorry you are so upset about this.

      I don't think I have ever been arrogant about Firefox. I feel the opposite actually - typical neurotic geek over here. So it's hard for me to understand what you mean: I think it's a humbling experience to be a dev in a big open source project like Firefox, I keep trying to do my best to improve the product so users like you will like it. When that doesn't happen, it makes me sad and I doubt myself. So I don't know why you think Firefox devs are arrogant - I feel exactly the opposite.

      Again, sorry that you are so upset about this. I wish I could do something to help.

    18. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Thanks for these comments. I was unaware of why Firefox was moving to a faster release schedule, I've never heard a reason why! If it weren't for the addons, I would have switched browsers by now, but now I can be more patient. You may want to suggest to the team publishing an in-depth article explaining WHY Firefox has moved to a rapid release schedule, it may calm a lot of annoyed users.

      They did explain it, just not on the release page when you installed 4.0 AFAIC remember. If you watch planet.mozilla.org or read TFA for some of the stuff that's been posted on Slashdot then you can see exactly this.

      The real problem is people who ARE aware of the reason (faster JS/rendering/HTML5 changes) and don't like it anyway. I'm going to echo the simple fact that standard=static, if the "standard" is changing constantly then it is not standard, it's a "working draft". [If I build a page using HTML4.01 then it will work in all browsers that support HTML4.01, if I write a page in HTML5 then there is a good chance that it won't work even in the same browser after the next couple of releases despite still saying "HTML5 supported"].

    19. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Using Firefox 1.6 when 2 was released: "Eh, more of a hassle than it's, wait, they changed WHAT? FFS, what are they smoking."
      Using 2.something when 3 came out "Oh great, I get a furry dancing armada with my freggin "upgrade". Can I get a browser that doesn't self-frag it's files to force the updates? Now half my plugins don't work"
      Using 3.65 when 4 came out "Jesus H Christ that looks gay. WTF? have they updated the last 3 updates?"
      Using 3.65 when 5 came out "I've seen version number masturbation before but jesus...banning firefox's update servers on my router...NOW!"
      Using 3.65 when 6 came out "How many morons are being taken on for this rollercoaster ride?"

      I don't care if you're going to push new features out like a bat out of hell but for fucks sakes do me a favor and version it in an intelligible way.

    20. Re:Rapid Release - a Tradeoff by Pascal+Sartoretti · · Score: 2

      There is a big tradeoff here, with downsides both ways.

      No, you got it wrong : people hare are not arguing about the frequency of FireFox releases, just on their numbering.

    21. Re:Rapid Release - a Tradeoff by lennier · · Score: 1

      Hi. Thank you, Mozilla developer, for your willingness to talk to us. Sadly, talk isn't enough, because it's not your talk we have a problem with but your actions. Explaining why you made a decision that a large chunk of your userbase directly and loudly asked you not to doesn't change the fact that you still went ahead and made that decision. In many people's dictionaries, doing something that breaks other people's work, and which isn't actually your decision to make, is exactly the definition of arrogance.

      That you somehow manage to still "feel" humble about your one-sided decision-making doesn't change that you actually did it. Sorry. I know you feel bad about being called the bad guy here, but that's because you are one of the bad guys.

      Or at least, you're one of the guys representing the organisation whose software is now no longer allowed to be supported by the IT division of the organisation where I work. Is that what you wanted? Dunno, but it's what happened, so perhaps you should try to understand why?

      Again, sorry that you are so upset about this. I wish I could do something to help.

      No, I don't think you understand at all. We're not upset about Mozilla's decision to abandon the enterprise. This has nothing to do with anybody's feelings. We're simply pragmatically and unemotionally dropping Firefox like the ticking security timebomb it has now become.

      See, your software used to be an asset in the Enterprise. Due to your colleague's decisions, it's now become a liability. That's usually considered a bad thing, no?

      The thing you could do to help would be to talk to your colleagues at Mozilla, and get them to reverse the decision they made. Primarily, make it so we in the Enterprise world can have long term security patches to Firefox separately to API breakage. We don't want new features. We want not to be rootkitted by every script kiddie who comes along. With what you've done, we now can't guarantee that. So, we're going back to Internet Explorer.

      There was a time, around 1999 if I recall, when Mozilla seemed to think that it wanted to compete with IE. Now it seems like you've shrugged and decided to abandon even trying to compete with Microsoft and just stay a home browser. That's fine if you want to do that, but some of us in Enterprise world would really, really, really, love to use Firefox at work -- and we were this close to getting authorisation to do it -- but now you've made it impossible. So, we're having to abandon you. I'm surprised that you're okay with this. I really am. But as I said, this isn't about emotions, it's about rational decisionmaking.

      If you want to have us as eyeballs and mindshare, please stop breaking our security patches (or write your software so it doesn't have zero-days in the first place, that would be super neat, but that seems to be impossible right across the industry right now, so we'll settle for patches like everyone else). But now that you've done the damage, it'll probably take about five years for us Enterprise types to trust you again.

      Does that help explain our problems with why merely feeling "humbled" at working for super-awesome Mozilla doesn't really cut much ice with us corporate IT types? What we'd like to see is actual actions. If you could take that message back to your colleagues, we'd be much obliged.

      Thanks.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    22. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Firefox nets itself $100m per year from the embedded search bar - that's before adding in donations/merchandise/etc. I'm not sure what your definition of little resources is, but $100m+ per year for working on what's been a reasonably stable web browser for quite a while now seems ample resources to me. To put that figure in perspective, a AAA title for XBOX/PS3 costs in the region of $20m - $50m over the entirety of its life cycle, which can be two or three years, that's for development, artwork, world building, game design, scripting, everything. $100m per year to polish a finished browser product seems like overkill.

    23. Re:Rapid Release - a Tradeoff by Tridus · · Score: 1

      Who are these people that were bothered by not having Websockets? Really? Users don't care. Admins don't care. Most developers don't care because the browsers are changing so fast keeping up is a full time job and they won't be ready to deploy anything using Websockets for another six months anyway.

      OTOH, lots of users are bothered by breaking addons. Corporate users everywhere are really bothered by the updates coming so fast that you can't bloody well test them. Everybody is bothered by the uglyness that is the current UI (which is still better then the hideous Thunderbird 5 one, I swear nobody tested that in Windows 7 and it was released half-baked because the schedule said so).

      The heart of the problem is that your users are unhappy, and you're listening to somebody else. Stop and listen to your users instead, and they'll tell you what a stupid idea this scheme was. You compete with Chrome by making a better product, not by releasing faster then they do.

      Until you guys start to understand what the problem is, I've stopped recommending FF to anybody (and our effort to get it at work is dead). If that was your goal, then congratulations.

      --
      -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    24. Re:Rapid Release - a Tradeoff by LateArthurDent · · Score: 1

      On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users. For example, FF8 will have much better memory usage than Firefox 4. Releasing new versions quickly lets users get that benefit quicker.

      That's not a bigger problem that annoy more users. Unless the user is encountering a particular bug, users considering having to upgrade an annoyance. When we open up the browsers to go to our home page and a window pops up that says, "there's a new release available" the instant response is "goddamnit, now I'm going to have to restart this thing". The only exception to this is if there's been something broken with the browser and we think, "maybe they fixed that issue."

      For new features, once a year is more than enough, once every six months if you want to be seen as fast moving (and, of course, if you need to release security fixes, then you release ahead of schedule, you don't have a choice there). In general, users don't like fast upgrades.

    25. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      How numbering like this: V.SV.BF where V is major version with major new features across the board, SV = Sub-Version which can include new technical features, and BF = Bug Fix???

    26. Re:Rapid Release - a Tradeoff by LateArthurDent · · Score: 1

      The problem is that Chrome and Firefox 6-week updates can and do change functionality and break internal APIs. Regardless of whether those browsers raise the major version number, addons can break.

      Well, stop that. It's not that you can't make those changes, but that's why there's a difference between everyone getting nightly trunk builds and actual releases. Keep any changes that break the API for yearly releases, and update the major version number then. Place any updates that are just security and bug fixes into a faster release schedule, and don't update the major version number for those. It's not that hard, it's pretty standard practice.

      Firefox is moving to allow that approach with the jetpack SDK.

      Which is great, but it doesn't change any of the above.

      However addons that don't use that SDK are relying on internal Firefox APIs, and the power and flexibility that that gives does mean they are at risk for breaking.

      Nobody is complaining that you guys are breaking those add-ons. We're complaining that you're breaking them too often. Just queue up those changes for a release that is on a longer schedule, just like you guys used to do.

      Honestly guys, being more like Chrome doesn't help you. The users firefox had that wanted Chrome are already using Chrome. You're about to lose those of us who haven't changed browsers for the precise reason that we don't like Chrome. Part of the reason we don't like Chrome is because their add-ons don't have the same advanced functionality firefox add-ons do, because firefox add-ons can use the internal API. Stop breaking those every six weeks, that's why we haven't left. Feel free to make changes that break them on a yearly or at most 6-month basis.

    27. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1

      The thing you could do to help would be to talk to your colleagues at Mozilla, and get them to reverse the decision they made. Primarily, make it so we in the Enterprise world can have long term security patches to Firefox separately to API breakage.

      I am trying to do just that. There are many people in Mozilla that think we need a long term support version (like Ubuntu) that would be enterprise-friendly. Hopefully we'll succeed. Btw, a lot of debate about this is going on at the mozilla.dev.planning mailing list which is of course public - so you don't need to be a Firefox dev to make the case for an enterprise version.

      If we don't, there will at least be some third-party enterprise versions of Firefox out there. For Linux there has always been Red Hat, and there is at least one company (I forgot it's name) about to launch a product for all OSes. But again, I agree it would be better if Mozilla did it.

    28. Re:Rapid Release - a Tradeoff by ceswiedler · · Score: 1

      I'm not sure if it still happens, but I was very put off after upgrading from FF4 to FF5 and then a couple of days later being told that Mozilla "strongly recommends I upgrade to FireFox 6 beta". Strongly recommend I upgrade to a beta?

      I don't mind the fast releases. But couldn't you call them version 4.5, 4.6, 4.7, etc? You're going against the grain of nearly every software project out there by bumping major versions so quickly.

    29. Re:Rapid Release - a Tradeoff by PybusJ · · Score: 1

      I do understand that there are evolving answers to these issues, but I'm not sure it was worth making the changes before you'd fixed the issues. Post 4.0 you could have made a concerted effort to develop add-on APIs and get extension devs to move over. Then switch to the new process once users extensions won't get disabled. Many, many users can live with not being faster than IE9, in return for stability and not having things break (and indeed not having UI change too often).

      I fear that by the time you've found a solution it will be too late: the power users who depend on add-ons will have left; Chrome will have expanded its extension API and more will have been created. I was already getting "what you're still using Firefox?" comments from other techs before FF 5. Firefox might have a large install base of less technical users now, but once the tech vanguard move on and stop recommending it you're in trouble.

      I have a feeling that Mozilla lives in its own little bubble where competing on features and speed, setting the standards pace, and "pushing the web platform forward" seems critical. I'm sure it all feels great in Silicon Valley, but not all web development happens in cool startups champing at the bit for the latest canvas 3D gizmo. I'd hazard that there's even more spread across businesses large and small. The type of business which doesn't move so quickly and can take a long time to adjust to any change. Many of us aspire to a stable, open source browser to act as a basis for the web, rather than a Chrome-clone.

      Sadly, I predict you'll all enjoy getting to do your cool vanguard standards stuff without that legacy support to worry about, but only for a short while, as your market share declines and any remaining competitive advantage is overtaken by a corporation with an agenda of pushing its own web-based services. I think the new process suits you more than it does most end users.

    30. Re:Rapid Release - a Tradeoff by PybusJ · · Score: 1

      Mozilla now has lots of engineers and has been hiring more. If you cared so passionately about these things you would allocate the resources to provide them.

      Instead you get developers of other systems dropping support for Firefox in their website/service/appliance to the same level as Chrome. i.e. we don't stop you using it but won't support it if you have a problem. It's sad to have to do it, but neither browser fits into standard product development and testing timelines. That's not a problem for huge websites with accordingly large resources, nor for the perpetual-beta start-up, but for everyone in between it's an issue.

    31. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1
      I agree the addon compatibility issue is a big problem, exactly as you said. Perhaps we should have waited until it was solved or much closer to being solved before doing rapid releases. It's hard to know in advance what timing is optimal for this kind of thing, and like everyone we make mistakes sometimes.

      However I don't agree with this part of your comment:

      I have a feeling that Mozilla lives in its own little bubble where competing on features and speed, setting the standards pace, and "pushing the web platform forward" seems critical. I'm sure it all feels great in Silicon Valley, but not all web development happens in cool startups champing at the bit for the latest canvas 3D gizmo. I'd hazard that there's even more spread across businesses large and small.

      Before FF4, everyone here on Slashdot and elsewhere were saying that Firefox was losing users to Chrome because Chrome was faster. And I think that was true to a significant extent - users do notice speed, and it gets a lot of attention by power users who recommend browsers to normal users. So it was a correct choice to focus on speed for FF4, and as a consequence, today people are saying that Firefox's weak side is something other than speed - because the speed issue is largely resolved, we are very competitive there now. So I don't think any "Silicon Valley bubble effect" had an effect on that choice. Anyhow, most of our developers don't live in Silicon Valley ;) (like most open source projects, we are very spread out)

    32. Re:Rapid Release - a Tradeoff by PybusJ · · Score: 1

      Yes, Mozilla needed to invest in Firefox speed, and did so in the FF4 cycle as you're doing so currently in Memory use. Firefox(1) currently works better for my 100+ tab browser habit than Chrome, so despite your older code base and smaller size I think you can produce a competitive browser engine even if you're playing catch up now.

      But I think you've way overcompensated for the FF4 development cycle. Face it, you were losing users to Chrome, and you will continue to do so. Chrome is a competitive browser from a well known name, backed by the kind of company that can drop $12B on an acquisition without breaking sweat. I see dozens of Chrome ads every day as I browse on Linux (they're on this page!). You just can't expect that not to affect market share.

      In reacting to this you seem to have pushed hard to produce a more Chrome-like experience. No-one objects to investment in speed, memory use, multi-process support etc., but Google is either ahead or capable of catching you in all of these. At the same time you're destroying your USPs. You must occupy a different niche to Chrome or you will lose.

      You used to have a huge add-on and customisability advantage, but as already discussed are damaging that (plus putting off the users who depend on add-ons -- if they do stay on FF it'll be harder for them to trust add-ons if they've broken before).

      You used to have a browser that competed with IE, not so good for enterprise use, but it was competing and it was cross platform. You're abandoning that for version free upgrades. That's too much external trust and too little control for most enterprises, who don't want the extra risk. Asa says web applications don't show versions, but we only use web applications where we have a business relationship with the supplier, have done our own testing on the site and have clear idea of its support; having such an external dependency is not taken lightly.

      You used to have the advantage of being Open Source, and the army of contributors who went with it. But webkit is open source too, and Mozilla is now pretty strict in what it accepts. If you want to add new functionality to web browsers it's certainly not harder to get code into Chromium.

      What is Firefox's Unique Selling Point now? The fact that you're tough enough to take a principled stand against H.264? I love you for it, I really do, but I know it's irrelevant to the world at large, even most of the tech world. It won't be close to enough.

      Maybe I'm wrong in characterising Mozilla's attitude, but your mission does seem to have become using the power that our browser share gives us to "do good for the internet". Which is not so very far from farting around worrying about the next big idea rather than serving your users best. I'm unconvinced you'll keep them; you're burning community goodwill like there's no tomorrow, and with them goes your influence.

      Seriously, what is your market positioning in comparison to Chrome, I really can't see it?

        (1) Today's bit of crazy is that version numbers are not webby enough, so I guess there's no point referring to a specific version any more.

    33. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1

      You make a lot of good points. I agree that Firefox would benefit from focusing on a niche not occupied by Chrome. What would that be, though? Are you saying we should find it, or are you saying that there isn't such a niche?

      From my perspective, Firefox fills the role of a 100% open source, 100% community developed browser. As an open source supporter, I believe the web needs such a thing. WebKit is open source too, but it is basically controlled by two massive corporations - Google and Apple, and it isn't developed as openly as Firefox. Also, Google and Apple include a lot of closed-source elements in their browsers, Google less so, but still - things from print preview to Flash itself are proprietary code included in Chrome.

      I don't know if you'd call that a niche. But it's the reason I think Firefox is important and why I'm a Firefox developer. It's hard to use for marketing purposes, though ;)

    34. Re:Rapid Release - a Tradeoff by Walter+Carver · · Score: 1

      The grandparent is a dick. I understand that this is a transitional period for Firefox extensions authors. That's not my problem. My problem is the direction the browser is heading.

      I was a happy 3.6 user. I skipped 4 and upgraded to 5. First thing I notice is that the status bar is gone and replaced with a line that hovers at the bottom of the page, showing the URL.

      That's the noob's way. That's how Safari and Chrome do it because they don't want to bother their users. Good for them, but I'm a power user and I want a power browser. I like being in control of my web experience.

      The status bar is a part of any sane application. It is intuitive. It gives feedback on what's happening. It's not that you gave us the choice of disabling it, we could already do that ages ago. You simply took it away from us.

      I know I can bring it back with an extension but that's not the point. This change was indicative of where Firefox is going. It's becoming a noob browser. If I wanted a noob browser I would use Safari or Chrome. I use Firefox because I want to have all the power extensions that allow me to control how things happen in my browser.

    35. Re:Rapid Release - a Tradeoff by PybusJ · · Score: 1

      Now, I agree with you 100%, but I don't think its a big enough niche to survive in. It appeals to slashdot readers (and only a subset of them) not the wider world.

      I don't think there is no possible niche, just that what you've moved further away from it over the last 6 months as you become more Chrome-like than Chrome (and it's possible it's now too late to change course).

      In one of my work roles I develop web apps and for many years Firefox was our recommended browser. It's cross platform, with good standards compliance etc. Chrome, when it came along, we didn't recommend; it seemed too much of a moving target. It was pretty standards compliant so likely everything would work; we'd collect bug reports and aim to fix them if possible, but not offer user support or claim it was tested. Now FF has made the decision to go with continuous roll out of new versions, it makes it hard for us to test and valid. And what's the point if by the time it's in users hands that version is obsolete. Once our tools are in use, just getting the funding agreement to make updates would typically take longer than a Firefox cycle. Now, as you remove version numbers from the users, even getting them to report issues to us becomes more complicated. You've become harder to support than Chrome. You've gone from the recommended option to below Chrome.

      We're not alone. My bank roles out changes to their site a couple of times a year. Currently FF 3.6 is what they claim to support. I wonder what they're going to do. I do actually appreciate the fact that they're cautious about updates and have testing and validation, no doubt slowed down by management and oversight, before they release changes.

      Not everyone appreciates change. In fact the majority don't. My partner, my parents, her parents, all use Firefox. They don't do so to get more features, faster and more often. They use it for security, and a trustworthy reputation, and in part to have the same browser on multiple platforms. They don't like change -- when I've been in the room and thing have changed due to upgrades they complain to me as the nearest tech. Asa says websites change without user's permission or knowledge, so why shouldn't browsers. I think that's a spectacularly bad argument since people around me don't like it when google or facebook make changes to their interfaces either. Users are totally unempowered to prevent changes to public web services at the whim of large corporations, that's no argument for taking it from them in their browser.

      What I read in the mozilla blog is all "Drive the Web Forward", "faster and easier". What many want is something they can trust to be there nice and stable. I think that ties well with Mozilla's open aims, more than continual upgrades, more than spending your hard-won trust capital on releases that break users' add-ons.

      I guess, I think there was a greater niche to compete as more of a cross platform, open source, extensible and customisable alternative to IE, than as a direct competitor to Chrome. I appreciate that's a bit less coo, but while I take you point about Mozilla being beyond the Silicon Valley bubble, I do think you're overly interested in the tech vanguard and it may well come home to roost.

      For now I continue to use Firefox (either beta or aurora), but I foresee a steady decline as Mozilla devs spend the diminishing Google Ad money on their increasingly irrelevant tech interests. On a brighter note, there's a reasonable future for said devs; Firefox will look great on their CV and no doubt the remaining megaCorps left to control the browser market will snap them up. It's us supporters of a free independent browser who'll lose out in the end.

    36. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1

      I definitely understand your criticism. I do feel it is overly pessimistic though, even if you are correct on the main points you make.

      But more than that, I do disagree with a main point: That you say users want stability and consistency over all else. To some degree it's true, they do want those things. But they also want other things as well. The fact that users want more features than the web currently provides can be seen in the success of Flash, for example, and in the mobile space, in that native iPhone and Android apps are much more successful than websites (or 'web apps'). So users do want those additional things, and when the web doesn't provide them, they go elsewhere.

      The problem is that those elsewheres are closed silos. Some more than others, but none is truly open or standards-based.

      We can keep the web where it is now, stable and unchanged, and innovate in those other places. There are upsides to doing that, but I strongly believe the downsides are much bigger: Our best hope for an open, standards-based future in computing is the web. The web isn't far from doing what those other platforms (Flash, iPhone native apps, etc.) can do, but it does need more work.

      Sadly the price of doing that work and innovation on the web is that things are no longer as stable as they were. But it's the best way to get to where users want things to be: They want to be able to buy the devices they want and run the stuff they want on them. The web platform will be able to provide that, but not the iPhone platform, the Flash platform or even the Android app platform. That isn't a silicon valley tech dream, that's a universal dream.

    37. Re:Rapid Release - a Tradeoff by PybusJ · · Score: 1

      Maybe it was too pessimistic a view. I certainly wasn't suggesting that Firefox should be preserved in aspic. I'm glad to see the progress: features such as canvas and usable typography are revolutionising web sites. I can see that in a year or so's time there might be all the features to replace flash. I want that progress; I just don't see the need to have 10 releases to get there rather than 2.

      There's a continuum in release speed between Microsoft in the IE6 days, and Chrome. If Firefox want's to be different from IE and Chrome, I don't think it should be at either extreme.

    38. Re:Rapid Release - a Tradeoff by SydShamino · · Score: 1

      For example, FF8 will have much better memory usage than Firefox 4. ... Meanwhile Firefox has released twice (counting FF6 on next Tuesday), and as a consequence, Firefox users have better performance than IE users, simply because IE users are still on IE9 while Firefox users can run FF5 and FF6 which include a lot more performance improvements that were committed after FF4.

      Those are silly examples. It's not like the Gods have decreed that better memory usage shall appear in Firefox 8, and thus you must move rapidly to that number.

      Why not just put the performance improvements in 4.1 and 4.2, and the memory usage in 4.7? Version numbers are arbitrary, except that Firefox forces addon compatibility checks with major releases. Now that major releases are too often, these checks are too annoying.

      And if you are claiming that you need to break addons every quarter to achieve all these objectives, and you see nothing wrong with that - well, you have bigger problems, the first of which is that you should put the product back into beta if you want that ability.

      --
      It doesn't hurt to be nice.
    39. Re:Rapid Release - a Tradeoff by SydShamino · · Score: 1

      Then Firefox should have given more time between the release of the SDK and the enforcement of its use, by delaying the time between Firefox 4 and the first subsequent release that broke something.

      --
      It doesn't hurt to be nice.
    40. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      Ok, I know this post is almost a week old, but I hope you get pinged by replies to your own comments..
      What really bothers me is that Mozilla decided to change the release process and numbering before Jetpack was ready for prime time. I have a slew of plugins which I would nothing more than to avoid having to maintain and fix every 6 weeks, but unfortunately there is currently just too much functionality missing in Jetpack to make it an alternative to ordinary XUL development.

      Even your own page positions Jetpack (addon builder / SDK) as intended for web developers, which I read to be an exact duplication of a problem which Greasemonkey and userscripts.org have solved years back now.

      What is currently missing from Jetpack is the ability to customize the user interface (add custom menus, icons), interact with other plugins, and some configuration point (UI) where end users can configure the Jetpack plugins. If / when you guys decide to kill off XUL entirely, then Jetpack might get some wind under its wings, but until you're ready to do that and eat your own dog food (develop FF without XUL), I don't forsee a single addon of renown is going to shift (too much invested and too many pieces missing).

      Don't get me wrong. I really like the idea behind Jetpack, but I haven't seen much development on it since it was introduced. The lack of development effort is unfortunately not something which gives extension developers confidence, especially with so many critical holes still remaining, and advocating for Jetpack as a migration path today or during the next 12 months is rather naive I fear unless Mozilla becomes willing to prioritize that project.

    41. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1

      I believe that you should not have to update and maintain your non-jetpack addon every 6 weeks! If your addon is hosted on addons.mozilla.org, it should be auto-scanned for compatibility before each update, and marked as compatible if it is. And in the majority of cases it should be compatible, since 6 weeks isn't enough to change very much, unless your addon happens to use APIs that are currently very much in flux.

      Regarding jetpack, I have not worked with it myself, so i really don't know much about it. But as I understand, it isn't meant to be able to do everything XUL can. Jetpack is purposefully very limited - like the Chrome addon API - in order to make it very stable and noninvasive (to the browser), so browser updates don't break stuff. So the APIs you are missing might be that sort of stuff - purposefully left out, as opposed to not yet developed - but again, I am not a jetpack user so I can't be sure.

    42. Re:Rapid Release - a Tradeoff by Anonymous Coward · · Score: 0

      So what you are in effect saying is that you don't envision FF as a platform for others to base their work upon. That is what unstable API means for binary distributed software. At least Linux has stated this up front and provided numerous advice how developers best cope with this fact. I've seen no similar announcement from Mozilla (and no, Jetpack isn't even close to being the answer atm.)

    43. Re:Rapid Release - a Tradeoff by kripkenstein · · Score: 1

      I think Linux is a good comparison: It also has no stable internal APIs, and no binary ABI, like Firefox currently does. For both projects, its important to do that to allow for quick progress.

      Mozilla did announce the 6-week rapid release schedule ahead of time. As I said before, I agree there are problems with it - but it was announced publicly, on the mailing lists, blogposts, etc.

  49. Re:STOP by fferreres · · Score: 1

    I still do. I upgraded in my other personal computer, and I didn't like the interface. It slows me down and didn't add anything I wanted. I am constantly thinking that I must upgrade and switch. Firefox has something that Chrome does not, my empathy. Forefox was the first browser good enough to enable me to switch from IE, and easy enough on corner cases to make me want to always use Firefox (Original IE Tab). So marginal improvement of other browsers that do not have the empathy I have for Firefox are just losers (until/if Firefox makes a big mistake).

    --
    unfinished: (adj.)
  50. Upgrade to FF3 by tfg004 · · Score: 2

    I tried FF4, but quickly upgraded to FF3.
    I tried FF5, but quickly upgraded to FF3 again.

    Since, imho, the user interface of FF3 is superior to its successors, I consider going back to version 3.6 an upgrade!
    I've got no plans to try FF6+ at all, until I read some good reviews convincing me the UI will indeed be an improvement wrt FF3 instead of a worsening like FF4 and FF5.

    1. Re:Upgrade to FF3 by Anonymous Coward · · Score: 0
      You can change the UI to look almost exactly like Firefox 3.6: Taming Firefox.

      That aside Gecko is faster and supports HTML5. On the whole I think Firefox 6 is better, but I think you can safely wait until Firefox 7 is out before upgrading.

  51. Re:STOP by Anonymous Coward · · Score: 0

    It's shocking just how out of touch Mozilla has become. This whole "clutter" argument from self titled "UI experts" is just tiresome now.

    Go use a netbook and you'd see when GUIs are cluttered and wasteful. It doesn't take a "GUI expert", it takes experience with a variety of devices and common sense.

  52. There is a lot of upset users. by Anonymous Coward · · Score: 1

    I have posted a lot on the issue. Firefox 3.6 is seen as the last "good" version by a large amount of users (Check how many posts about people staying on it, plus market share reports show a lot of 3.6 users).

    People don't want to have to use extensions and hacks to get back their status bar or themes, so they rather stay on 3.6 or switch to a web browser that listens to its users.

    There are people who have supported Firefox back when it was Phoenix/Firebird or even plain old "Mozilla" and feel that since 4.0 that Firefox has been hijacked by developers who are not listening to their users. The same impression is with GNOME 3 which even Linus himself has decried.

    The solution is so simple, just offer the status bar without extensions, by including it in "Menu, view, status bar". Opera, Safari IE9 includes status bars as OPTIONS. The next thing is to keep rapid release for features, but don't needlessly break the extensions and don't exaggerate the version numbers.

    Remember Slashdot users supported Firefox in the early to get us off IE6, but it looks like Firefox will become the new IE6 if the developers don't listen to the user base who made Firefox successful in the first place. Hopefully Mozilla will come to its senses when Google Stops giving them funding and they will have to actually compete for donation money again.

    1. Re:There is a lot of upset users. by Tacvek · · Score: 1

      Of course the loss of the status bar does not mean much. While the original 4.0 did not, later releases added in a chrome style URL bubble down at the bottom. (visible only when hovering over a link). Since that, the progress bar, and extensions were all that were ever in the status bar, and since the addon bar at the bottom can hold extensions, the only thing missing is a bottom progress bar.

      If you don't like tabs on top, or the menu button, it takes less than a minute to revert both. Finding a nice theme for that configuration should not take more than a few minutes either.

      However, there is a very good reason why Chrome, Opera, IE and Firefox are all converging on a similar look and feel. I strongly recommend that everybody seriously try using it for a while, and see if it really bothers them.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    2. Re:There is a lot of upset users. by surveyork · · Score: 1
      --
      2019 is going to be the year of Linux on the desktop.
  53. Re:STOP by Nemyst · · Score: 1

    Out of curiosity, I've tried rearranging the interface mostly as it was in 3.6.

    http://img221.imageshack.us/img221/597/ff5.png

      It is visually different, but that's what themes are for. You have no reason to stick to an old browser like 3.6.

  54. Open source projects can't shit on their users. by Anonymous Coward · · Score: 0

    Regardless of what you guys think you're doing, the Firefox community basically sees you guys as shitting all over our faces, and we're not interested in playing this dirty game.

    Open source projects that mistreat their users like this don't survive. Look at pre-EGCS GCC. Look at XFree86. Those are two good examples of open source projects where the developers starting dumping load after load of shit upon the users.

    My understanding is that some of the Firefox developers are still in their teens, so if you're one of them, let me just explain what happened to the aforementioned projects. Basically, the users fled. In time, EGCS replaced the initial GCC effort, eventually being renamed to GCC. Xorg absolutely crushed XFree86.

    The same is likely going to happen with Firefox. It may not be apparent now, but things can change very quickly. Firefox could easily find itself with down to just 1% or 2% of the market within a matter of months, if these shenanigans continue.

  55. Re:Firefox has been fired. by Anonymous Coward · · Score: 0

    LOL. Firefox is really a fork of Seamonkey.

    And Seamonkey came from Netscape.

  56. Re:STOP by visualight · · Score: 1

    That's bullshit and you know it. This "cluttered GUI syndrome" started well before anyone was using netbooks or touch screens.

    --
    Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
  57. Re:STOP by NickFortune · · Score: 1

    The thing I like about firefox is that you can completely rearrange the interface. For me every version has looked the same.. I don't really care what they do with the default settings.

    I know they keep making harder to find out how to put it back the way it was.

    I get fed up of playing "hunt the toolbar" with each new version.

    I swear, it's like every release, someone at mozilla has said "right: which of the features that made our browser popular can we get rid of this time?"

    Am I really the only one who'd jump at a chance to run 1.2 or thereabouts with modern security updates? A genuinely lightweight browser, everything easy to move around, and all the complicated stuff in addons where it belongs. First browser I get that does that and still lets me install equivalents to adblock, noscript and cookie safe, and I am so abandoning Firefox.

    --
    Don't let THEM immanentize the Eschaton!
  58. My solution by Anonymous Coward · · Score: 0

    Mod parent up!
    "While you may not think it affects you now, I think you will soon see things like banking sites that go back to only supporting IE"

    The sole reason why IE owns 90% of the market in Asia is because of banks using activeX. If banks and other corporate institutions only support IE then we are back to square 1 again and this will harm everyone.

  59. Re:STOP by Lanteran · · Score: 1

    6 is basically 4.0.0.0.2, and I can change my style back to 3.6ish on 4-8 (nightly).

    --
    "People don't want to learn linux" hasn't been a valid excuse since '03.
  60. Re:Firefox has been fired. by gottabeme · · Score: 1

    "This is accomplished by no longer caching previous pages (so if you go back, you'll have to reload from scratch.)"

    Um...did they remove the caching completely? If so, that's not progress. It was a great step forward when they added it.

    --
    "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  61. Re:STOP by Lanteran · · Score: 1

    Nope, GNOME 3 can be heavily customized as well, even to look like 2.x to a degree.

    --
    "People don't want to learn linux" hasn't been a valid excuse since '03.
  62. An Idea by Billly+Gates · · Score: 1

    If you work for Mozzilla, I would like to make a suggestion.

    Consider an Enterprise Edition of you product where you can do something like Firefox Enterprise 4 with fast releases like release 3, release 4, etc. This way you can still have agile development but can milestone it with corporate support and the plugins will not break. The customer can choose which release to upgrade. A year and a half later you can put put out Firefox Enterprise 5 release 1, ... etc.

    Or call it Firefox professional if you want more people to use it. They can select in the options menu whether they want a later release or not.

    In many ways it is what Redhat does with Redhat Enterprise Linux and Fedora. Fedora code eventually enters Redhat Enterprise after 2-3 years and users are free to choose one or the other. Or that is an idea as well. It wont increase development costs as Firefox Pro is simply Firefox 4 and each release in it is Firefox 5, and 6.

    Face it, it doesn't matter if html 5 and css 3 is the coolest thing ever! If 20% of users use older more mature browsers that are 5 years old like IE 8 then no webmaster will use it. Then who looses? The advantage then for using Firefox is gone because no one uses the cool things you do to your browser because they have all switched back to IE so why choose Firefox?

    My biggest fear is that places like banks will only support IE and once that happens ActiveX and other things will come in and force everyone else to use IE like in Asia. That would be terrible.

    Just an idea and I do not know how much of a pull you have, but I would advise you to bring it up fairly quickly before you loose corporate clients forever. They are leaving fast.

    1. Re:An Idea by kripkenstein · · Score: 2

      I agree a corporate-friendly version is important. It's a lot of time and effort, though - Red Hat does it well, but then that is exactly Red Hat's prime mission, supporting a rock-solid OS for a long time. It might be possible for Mozilla too, but it would be a lot of effort, which worries me.

      I'm not too worried about IE cornering the enterprise market, though. For one thing Apple laptops are getting very popular there. Also enterprise users are starting to do more and more browsing from smartphones and tablets. And Google is pushing Chromebooks into that market (but I have no idea if they will succeed). So overall I still think Mozilla should do more for enterprises, but regardless IE will not dominate that market more than it already does, banks will want people to be able to visit them from iPads and Android phones and MacBooks.

    2. Re:An Idea by Anonymous Coward · · Score: 0

      Wow, a real reply from Mozilla thanks.

      Another idea is charging $59 for the enterprise/professional edition for support. This could be used to raise money for the added costs, in addition to funding Mozilla. You can then sell it at retailers similiar to Netscape's Gold Edition. Maybe throw in a 5 user pack for $100 and more discounts for larger installations. Most of your QA costs will come from people using the regular Firefox rapid release schedule anyway. The costs are pretty cheap as the corporate or professional edition will be biggypacking at the other releases. Bugs will be fixed beforehand in the other release being committed in.

      Many corporations think free software = liability and assume anything free is GNU which is a liability thanks to SCO/Microsoft. Or they are afraid the BSA will try to charge them for Firefox. A paid version eleviates these issues.

  63. Re:Firefox has been fired. by Samantha+Wright · · Score: 3, Informative

    No, they didn't, and that was a bit of an overstatement. I think some things expire according to staleness, though, and there have been a few occasions where backing up through a form submitted by POST resulted in the browser fetching the page via GET without mention of any of the POST headers. If you want to know the actual and intended status of things, here might be a good place to start researching.

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  64. Nothing Like Mozilla's Browser Release Schedule... by Anonymous Coward · · Score: 0

    ...to get me to IMMEDIATELY switch to Chrome.

    Way to go Mozilla. I was a faithful zealot until recent developments made your development schedule run like Charlie's Chocolate Factory.

  65. Re:Firefox has been fired. by iggymanz · · Score: 1

    properly speaking, forked from the Mozilla Application Suite, as was firefox

  66. I like it. by Anonymous Coward · · Score: 0

    I for one like the new version, and I like the rapid release cycle. I also don't use a ton of plugins and extensions. There is nothing stopping people from sticking with older versions.

    I guess I just don't fully understand the animosity. It is after all a FREE product.

  67. Re:Nothing Like Mozilla's Browser Release Schedule by Anonymous Coward · · Score: 0

    Enjoy your useless adblock

  68. Same reason people stand in line for iPhones by p51d007 · · Score: 1

    It is the "instant" gotta have it now" mentality that people from their teens to their 30's have these days. Heck, get a bunch of kids around an old fashioned ice cream churn and tell them they have to turn it for about an hour before they can have ice cream...they'll say screw it, and go to an ice cream store. People can't wait anymore, no patience, no manors, rude, in a hurry. Kind of like the old bull & the young bull sitting on top of a hill overlooking a heard of cows below. Hey old man...lets run down there and screw a couple of those cows. Old bull says, yeah, or we could slowly walk down there, and screw em all. Personally, I'll wait a week before I update, if anything else (bugs in a x.0 release), I want my plugins to NOT BREAK. Hopefully, after a week, the ones I use will be signed to work with 6.x

  69. Re:Nothing Like Mozilla's Browser Release Schedule by Christopher+Fritz · · Score: 1

    Is Chrome any better in this regard? Honest question. I've heard others talk about it having a rapid release schedule (before Firefox moved to one). And how do Chrome and Firefox compare on UI changes per release?

    My mother uses Facebook and plays Bejeweled on it. Recently, there are massive lag times of a few minutes for some actions, such as sharing points. This lag isn't there with Firefox, and many of my mother's friends who play use Chrome. I installed Firefox on my mother's laptop, from this page here, but apparently that is the version four installer, and Firefox is nearing its version six release...

    Rather than trying to customize Firefox 4 to look like Firefox 3 on my mother's PC, I told her the user interface (I gestured to the top area of Firefox we had open on her PC) would look a little different. It shouldn't affect anything my mother does to have the interface look a little different. Thanks to Firefox's interface becoming more Chrome-like, if Chrome is any better with memory use than Firefox, the day might come when I'm installing Chrome rather than Firefox for my mother.

  70. Fork? by desert69 · · Score: 1

    I can understand companies not being in touch with their customers, but does Mozilla not even read tech sites like Slashdot? Every story about Firefox lately is filled with exactly how negatively people feel about this version number fiasco.

    Never read the word "fork" until now in all those comments. Free software, what are we waiting for?

  71. shit by Anonymous Coward · · Score: 0

    I'm still trying to get all my extensions working in 5!

  72. For those who like old school looks by surveyork · · Score: 1

    Firefox 3 theme for Firefox 4+ https://addons.mozilla.org/en-US/firefox/addon/firefox-3-theme-for-firefox/ and Winestripe Realfox 4 (makes Firefox 4+ look like Firefox 1.5) https://addons.mozilla.org/en-us/firefox/addon/winestripe-realfox-4/ There's also Pale Moon http://www.palemoon.org/ , which keeps the status bar and tabs below location bar by default. Anyways, Firefox's 4+ GUI can be reverted almost totally to the old style with a few clicks.

    Enterprises and users who don't like the fast release pace could try SeaMonkey http://www.seamonkey-project.org/

    --
    2019 is going to be the year of Linux on the desktop.
  73. In Firefox 8 by surveyork · · Score: 1

    You can grab a nightly 64 bit version meanwhile https://nightly.mozilla.org/

    --
    2019 is going to be the year of Linux on the desktop.
  74. ffs this is ridiculous by smash · · Score: 1

    Just use a time_t datestamp and give up the completely bogus version numbering.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  75. This has been coming for a while now. by nixkuroi · · Score: 1

    Firefox is getting close to the day where Google stops donating ... er advertising with them to the tune of millions a year (http://techcrunch.com/2008/08/28/mozilla-extends-lucrative-deal-with-google-for-3-years/) . At the end of that, they're going to be sitting in a version hole compared to their benefactor's product which is now a direct competitor. It seems to me, FF is doing whatever is necessary to make themselves look competitive when all of their opponents a) own the browser space on their own devices, b) own an OS or two that supports that browser natively and c) can get away with it because they all have monopolies in their own spaces but which all fall under a single general computing umbrella that makes them seem less like an overall monopoly.

    Mozilla is in an extremely unenviable position of looking old and outdated because of any kind of real mobile support, behind in version numbers compared to ALL other browsers (ie9? Opera 11.5? Chrome 1.5 billion?). I remember when Firefox defiantly announced that they wouldn't support the iPhone when even Opera was able to make it work. Do I use Opera on my iPhone? No. Does it remind me that Opera is still relevant in the mobile space? Yes.

    Mozilla is starting to remind me of an aging child star. This version thing is just them acting out to get attention. There's no reality shows for old browsers though, so they'd better start figuring out how to ingratiate their plugin developers or their only supporters are going to start writing Chromebug (Whaaaa? http://blog.getfirebug.com/category/chromebug/) and Ubiquity (Nahhh...hey! https://github.com/cosimo/ubiquity-chrome/)

    It's not too late. Firefox could still release its own tablet (http://www.tomsguide.com/us/firefox-mobile-firefox-fennecomb-android-tablet-ipad,news-11489.html) - but they're going to have to do it before the money starts running out and that's going to require community support, plugin developers and everyone that they're alienating with these most recent moves.

  76. Mozilla doesn't even read their own forums! by Anonymous Coward · · Score: 0

    I can understand companies not being in touch with their customers, but does Mozilla not even read tech sites like Slashdot? Every story about Firefox lately is filled with exactly how negatively people feel about this version number fiasco.

    Just search for "thunderbird tabs" and you'll soon come across a HUGE thread on the mozilla forums where dozens of people are complaining about the monstrosity which is tabs in thunderbird. Of course not ONE comment from any Mozilla developer.

    And you know what the weirdest thing is? I also got fed up with Firefox and Thunderbird. Kept using version 3 for a while but gave up and moved everything to SeaMonkey. Last week I pressed control-t by accident in SeaMonkey while reading my e-mail and suddenly discovered that it too supported tabs in the mail client.

    Yet in such a way that it didn't got in my face for nearly 4 months before I accidentally discovered that it was supported. I still don't use this feature, not my point, but why can SeaMonkey come up with a non-intrusive way to add tabs and Thunderbird cannot ? While its all build under the Mozilla umbrella.

    Madness, that's what it is IMO.

  77. Re:STOP by The+Dawn+Of+Time · · Score: 0

    It's shocking how your argument can be immediately turned right back on you - with the addition that you aren't actually delivering a browser, just talking out of your ass.

  78. Ahead of schedule by rossdee · · Score: 1

    So no chance of all the add-ons working then.

    I'll stick to the previous version

  79. Re:STOP by visualight · · Score: 1

    Actually no. I am right and you are wrong. You just have to think farther than "I like firefox" vs. "I no longer like firefox".

    At first their decisions were motivated by a need to gain market share, now that motivation is no longer prime. They only need to keep what they have -and that they will likely do no matter how many users get pissed off. They have crossed a tipping point and they know it. You can actually see the hubris behind their reasoning whenever they explain it (or defend it as anonymous cowards on /.)

    Also, delivering or not delivering a browser is completely irrelevant to my assertion, and to speak to your underlying premise, it's not like firefox is an effort dominated by volunteers "scratching an itch". They are paid, many are paid well, and they are paid indirectly by their users.

    That means I get to bitch. Deal with it.

    --
    Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
  80. Too many recent versions by BlueCoder · · Score: 1

    I don't know about everyone else but the inflation of the major version number is making me less confident in Firefox. It appears to me they are confusing the use of version and subversion number and sub sub version numbers. What happened to the old days when they increased the major version number no sooner than a couple years? Maybe it's time to get away from version numbers and use release dates instead.

  81. Fixes before numbering by a0me · · Score: 1

    Switched to Chrome a few months ago and never looked back. Firefox is still slower than Chrome; I don't know about the rendering, but the UI is a lot snappier with Chrome, even on older (5-6 years) machines. Firefox new numbering breaks plugins on a regular basis. I don't really see what's the point in using Firefox anymore.

  82. Re:Thrashing by Anonymous Coward · · Score: 0

    Linux is just too damned good an OS to be forced to act like a Windows user and hit the power button. I refuse to run software that makes Linux act like Windows.

    It sounds like Linux is not too damned good then. Maybe you should refuse to run an OS that lets software make it act like Windows.

  83. F6 behaviour by Neil+Boekend · · Score: 2

    Did they fix the F6 behavior? In previous versions, when you pressed F6 it selected the address bar. In 5.0 it did something else (seems to do something useless with frames) and I could not find the about:config item to fix it.

    --
    Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
    1. Re:F6 behaviour by Anonymous Coward · · Score: 0

      Did they fix the F6 behavior? In previous versions, when you pressed F6 it selected the address bar. In 5.0 it did something else (seems to do something useless with frames) and I could not find the about:config item to fix it.

      it selects the tab, not the address bar

    2. Re:F6 behaviour by adrenalinerush · · Score: 1

      In previous versions, when you pressed F6 it selected the address bar.

      You can still press Control-L (for Location) to select the address bar. Similarly, Control-K selects the search bar.

      Yes, I know that F6 selects the location field in IE and the File Explorer on Windows as well, so F6 would be more consistent. I'm just saying that there is still a keyboard shortcut to select the address bar.

    3. Re:F6 behaviour by BenFenner · · Score: 1

      I have Firefox 5.0 on this machine. Pressing F6 brings the focus to, and highlights the text in the location bar.
      As does Ctrl+L

    4. Re:F6 behaviour by webheaded · · Score: 1

      In Firefox 5 it appears to select the tab bar. Or at least that is what it does for me.

      --
      "Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
    5. Re:F6 behaviour by Anonymous Coward · · Score: 0

      Ctrl+L does the same thing. Just random, general, FYI.

    6. Re:F6 behaviour by Anonymous Coward · · Score: 0

      F6 selects the address bar in FF5 on Win7 for me.

    7. Re:F6 behaviour by Anonymous Coward · · Score: 0

      I'm using firefox 6 on GNU/Linux and F6 selects the address bar (however I'm using a patched version with KDE integration so YMMV)

    8. Re:F6 behaviour by SydShamino · · Score: 1

      Pressing F6 seems to select the address bar in FF6.

      --
      It doesn't hurt to be nice.
  84. Re:Rapid Release - new suggestions by Anonymous Coward · · Score: 0

    Hello, Well, it's good to have some explanation from a FF dev. On the one hand, it is good to see that the FF is pushing the cutting-edge technology forward; but, on the other hand, it is also true that we have a huge proportions of the users who do not care about these cutting-edge improvements. They want to see the FF working, same as it did before with their older versions! In light of this, may I suggest the following: STOP auto-updating the browser! Instead, push the auto-update after a sufficiently long time the new version is released. It will make sure that most of the extensions have caught up to the new release. You may use some script to check the incompatibility of the currently installed extensions. If many extensions are incompatible, don't push the auto-update, yet. However, you may use a small update notification icon that describes something like this: New version of the browser is available: m/(m+n) extensions are compatible; n/(m+n) extensions are not compatible. You may also include the names and short description of the compatible and non-compatible extensions. If you have any security update, you can also state it clearly in the update notification. If all (well, most) the extensions are compatible, push the auto-update. Otherwise, leave the update issue on the user. To make the above system functional even with non-mizilla-hosted extensions, you can require the extension devs to provide a method, so that the FF can check if they have updated the extension to be compatible with the new FF version. The above method would also give the stability-concerned users some relief.

  85. Re:nightlies by TaoPhoenix · · Score: 1

    Hallo.

    I used to avoid them as well, for reasons lost in the mist... but somehow FF5 or so suddenly went into a big cleanup mode after shutting down on my home machine. ("FF is still open .... "). Total showstopper because of my habit of close&speed-reopening the browser after a task. So I drifted into some of the FF spinoffs like Pale Moon to buy time.

    However someone's comment that they are indeed working on the memory footprint bit is mostly true, so I grabbed a nightly just now and I think it or another one will fix that problem. So maybe to get the "old feel of a nice set of features per release" I might just park on this Nightly, let the world turn, then "one day wake up and install FF8". By then the Nightly will prob be FF11 or something.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  86. Re:Rapid Release - new suggestions by Anonymous Coward · · Score: 0

    Hello,

    Well, it's good to have some explanation from a FF dev. On the one hand, it is good to see that the FF is pushing the cutting-edge technology forward; but, on the other hand, it is also true that we have a huge proportions of the users who do not care about these cutting-edge improvements. They want to see the FF working, same as it did before with their older versions!

    In light of this, may I suggest the following:

    STOP auto-updating the browser! Instead, push the auto-update after a sufficiently long time the new version is released. It will make sure that most of the extensions have caught up to the new release. You may use some script to check the incompatibility of the currently installed extensions. If many extensions are incompatible, don't push the auto-update, yet.

    However, you may use a small update notification icon that describes something like this: New version of the browser is available: m/(m+n) extensions are compatible; n/(m+n) extensions are not compatible. You may also include the names and short description of the compatible and non-compatible extensions. If you have any security update, you can also state it clearly in the update notification.

    If all (well, most) the extensions are compatible, push the auto-update. Otherwise, leave the update issue on the user.

    To make the above system functional even with non-mizilla-hosted extensions, you can require the extension devs to provide a method, so that the FF can check if they have updated the extension to be compatible with the new FF version.

    The above method would also give the stability-concerned users some relief.

  87. Re:Firefox has been fired. by Xest · · Score: 1

    "1. Memory leaks have been a major issue of recent Firefox development. Current FF 8 nightly builds use a tiny fraction of older versions, and they're extremely stable. This is accomplished by no longer caching previous pages (so if you go back, you'll have to reload from scratch.) I've got a cool 200 tabs open right now in a very old session and it's only using about 500 MB of RAM. "

    That's great, it's just a shame it's too late for me, as just last week FF5 managed to completely lose my ~200 tab session which was the final straw.

    It's nice they've finally realised this is an issue, but for 3 years of memory leaks and slow downs it's just too little too late. It used to be great, then it became bearable, but still better than the alternatives. Now it's just shit.

    Requiring a 3rd party addon to restore a basic staple UI element? No I'll pass thanks.

  88. Re:Firefox has been fired. by jbonomi · · Score: 1

    Just curious, but I always see people say they have over 100 tabs open at a time in these threads. How do you manage all of them? At what point is it simply not useful to open one more tab? Are you actually frequently looking at each of these tabs? I find over 15 tabs to be annoying at best. I just have trouble understanding how you're actually using the software. Are they spread out over multiple windows at least?

  89. Re:nightlies by Samantha+Wright · · Score: 1

    That version jump sounds about right. One version for Nightly, one for Aurora, one for Beta, and one for release. Hmm. It might actually be FF12...

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  90. Re:Firefox has been fired. by Samantha+Wright · · Score: 1

    I used to be a 30-tabs-in-two-windows type of person, but I increased my tab usage dramatically when TabCandy (now Panorama) was added to the Nightlies. I keep one tab group open for every major task, and type fragmentary URLs in the address bar to switch between them. The system's not perfect, and I've noticed that sometimes when I set out to do something purposeful I'll end up nearly duplicating a tab group in a separate window, but it keeps a lot of slowly-progressing activities and reference sites close at hand. This sort of practice is made somewhat easier by Firefox's tendency to not load old tab groups in the background after an application reopen until they're actually accessed by the user; until then they're just thumbnails, titles, and URLs.

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  91. Still Cannot Remove Crap? WTF!? by BrendaEM · · Score: 1

    What's the matter with the mozilla devs? Why must users tout broken and useless crap in their browser? How much money are they getting paid NOT to disallow users from uninstalling crap from their computer. WTF.

    --
    https://www.youtube.com/c/BrendaEM
  92. Re:Opera by obsess5 · · Score: 1

    "... leaving us with not so viable alternative - the Opera."

    I've been a happy Opera user (Linux and Windows both in the past, but now Windows mostly) for over 10 years - used to have to buy it, but well-worth its low price back then. FF is dirt slow on my old XP machine and IE8 seems equally slow; I only boot them up when a financial web site uses browser-specific pages. (For example, at work, I was one of the few Linux users and our electronic timecard system only worked in IE, so I purchased Crossover to run IE - booting up into Windows just to fill out my timecard was a non-trivial option, as has already been hashed out by work users in the recent "boot time" discussion.) I haven't been bitten by the Chrome bug since Opera has been lean and mean for all these years and I haven't found any need to change to a new browser.

  93. Re:Firefox has been fired. by Xest · · Score: 1

    First thing I do on a morning is scan through my favourite news sites- BBC, Slashdot etc. and check the headlines that are interesting, I open each in a new tab that sounds interesting.

    I tend to program at work in 30minute time slots, then take a 5minute break, during those breaks, at lunch time and so forth I'll have a look through the news tabs I opened up. Sometimes I wont bother to read more than the introductory paragraph if the story isn't as interesting as it seemed, other times I'll read the whole thing.

    Some days I open up more stories than I can read, other days I read more stories than I opened. Sometimes I have 200 tabs open, other times I manage to eliminate all but maybe 10.

    It's not just news stories, sometimes I open tabs to read later that contain longer articles, and you can't get through these in 5minutes. These tabs tend to hang around for weeks, sometimes months before I get round to reading them. If they've been there too long, like, 3months+ and I get round to it, I'll just bookmark them into a "To read later" folder.

    Sometimes also if I'm looking for a solution to a problem on Google and there's say, 8 useful posts about my problem on the first page, I'll open up all of them, then sometimes read the first one, find it solves the problem and get on with what I was doing, forgetting to close the other tabs, but I usually notice them again within a day or two and just close them.

    So some of it the answer is that I simply don't manage it well- i.e. those I forget to close immediately. But much of it is that I basically hoarde useful pages in tabs, and eliminate them bit by bit.

    It's not hard to work through the tabs to find what you want- click the tab dropdown to the right of the tabs and anything with a BBC or Slashdot icon or whatever is a quick story to eliminate in my 5 minute breaks!

  94. Re:Firefox has been fired. by Anonymous Coward · · Score: 0

    I am one of those that can have 100+ tabs open.

    I middle click / ctrl-click to open new tabs for future viewing. I'm basically using it as a queue (I have actually been looking for a queue plugin, but didn't find any). Most of the time, I am on the leftmost tab, or close to it (pages with lots of links sometimes get moved to the left of my active tab, and wait until I have closed all the tabs to the right).

    When I close a tab, I continue on the one just to the right of it. New links get opened to the far right, so it becomes a FIFO structure.

    The 100+ tabs is usually reached when I start at a page with lots of links to pages with pictures. So I can open 10-20 tabs containing pages with pictures, each with 15-20 thumbnails, and when I go through those pages, I open new tabs with the pictures the thumbnails pointing to. 10 pages with each 20 thumbnails gives 200 pictures. Not all of them are worth opening, but 100+ is likely.

    Why I don't right click on thumbnails and choose "save link target as"? Because then I would have to go through them later to decide which ones are keepers. With them waiting in tabs, I can quickly see if a picture is a keeper or not, and only the keepers get saved.

    A queue plugin, putting the links into a queue when middle clicked, and opening new tabs when old ones are closed (with a few (5-10) always open, to make switching fast) would be an alternative solution, but last I checked it didn't exist.

  95. IE 6 says it all about your bank by Anonymous Coward · · Score: 0

    BAD and hackable

  96. Time for some about:config diving by embolalia · · Score: 1

    Looks like they've gone with graying out all of the URL except the domain name, which seems popular these days. Too bad it's dreadful. I mean, it's not hard to find the domain name in a URL. But when you gray it out, it makes the rest harder to read. So if, like me, you occasionally manually change a URL for whatever reason, it's a pain. Or if you /do/ care whether you're using http or https. Hopefully it's changeable...

    1. Re:Time for some about:config diving by Anonymous Coward · · Score: 0

      about:config, search urlbar, it's the 'formattingEnabled' key.

      And I'll add one - when you browse intranet sites (at least until work forbids Firefox again because the latest 2 versions are on the list that takes 3 and half months to get on) it's a huge pain to have the parts of the URL that CONTAIN USEFUL INFORMATION grayed - I want to see paysystem.somecompany.com vs. internalblog.somecompany.com - if you want to gray something, gray somecompany.com.