6 ms·

Unless they have the quick, silent updates of Chrome AND the (so far) perfect quality control of Chrome, these quick releases do more harm then good.

by sapper2 15y ago

dpcan 15y ago
I JUST downloaded FF4 and now I see 5 is coming out. Version-less updates of browsers makes sense, and they should be seamlessly, silently, updated in the back-ground. This is getting crazy. I install Firefox for friends and family who I want off IE, and this actually embarrasses me a little. If I have to keep telling them to update, they will quit - or end up using REALLY OLD versions of Firefox and we'll have an IE6 situation all over again soon but with Firefox. I'm starting to install Chrome now. At least I can say that their browser will always update, and they have nothing to worry about.
- jcitme 15y ago
  if Firefox 17 came out 3 months ago and we are currently on Firefox 20, I don't think that's any less secure than running 3.6.5 when 3.6.7 came out...
- code_duck 15y ago
  Firefox has always done a good job of handling updates. It is not in the background, but it is painless and automatic once you agree to upgrade. It will never be anything like IE6 - how many people do you see using Firefox 2? or even 3.0? The upgrade to 5 isn't much different than going from 3.8 to 3.16. Mainly, they've changed their numbering scheme, so there's no reason to make a big deal about it.
- thomas11 15y ago
  Firefox 5 is not coming out. It's a beta. You shouldn't bother friends and family with it.
  - rsoto 15y ago
    Actually, my Firefox it's advicing me to update. And I'm not on the nightly, developer or beta channel.
    - thomas11 15y ago
      Strange, mine (4.0.1) doesn't. There's something broken either in the update routine or in your Firefox. The beta is not supposed to be recommended to users of a release version.
      - rsoto 15y ago
        Yeah, I'm also very confused. While I think it's a good idea to be pushing relases more often, this is way too often. Here's the about Firefox dialog http://i.imgur.com/cDbN1.png http://i.imgur.com/cDbN1.png and the update request http://i.imgur.com/4SYRI.png http://i.imgur.com/4SYRI.png
    - zpao 15y ago
      Are you sure you're not on the beta channel? Coming from Firefox 4, that channel stuff was under the hood. If you used Firefox 4 beta, then you're probably on the beta channel (you can check in about:config looking at app.update.channel)
redemade 15y ago
seriously... WHY aren't other browser vendors adopting the chrome release strategy?
- horser4dish 15y ago
  There's still a market for people who want to manually upgrade. There was a comment thread on HN a few months ago about this as well (no way we'll be able to find it now, I don't remember the story), but it summarized my views very well. I like knowing what is or isn't being installed on my computer. I've got a bash script to automatically download and update to the newest Firefox, so the act of upgrading isn't a chore. But I don't want a given company, be it Google or Mozilla, to arbitrarily change what's on my computer. That's not to say I don't see the allure of automatic updates, but I just don't want them to be silent and mandatory.
  - kijinbear 15y ago
    Given how configurable Firefox is, I'm sure they'll add an option to disable automatic updates even if it becomes a default feature.
  - richbradshaw 15y ago
    For a web browser there is no reason not to want to use the newest build, especially while HTML5 and CSS3 are being actively implemented. Your bash script is just your own version of Mozilla's auto updater.
    - horser4dish 15y ago
      Sure there is. A while ago, while I was using the 4.0 beta, I ran into a problem: modal dialogs wouldn't work. In beta 4 they worked just fine. Beta 5, just fine. When beat 6 rolled around, they stopped working. I reverted and used that until beta 12 fixed my problem. 6-11 were useless for some of the things I used it for (example: TiddlyWiki editing) because Javascript alert() and confirm() dialogs would literally not show up. EDIT: also, the bash script is there because I install Firefox to /usr/local, and it's easier to type "update-firefox" in an already-open terminal than to reboot Firefox as root so it can modify my files. I'm aware it's redundant, but it also a) requires my active participation, so I can't miss it and b) lets me downgrade, in case of something like what happened above.

Unless they have the quick, silent updates of Chrome AND the (so far) perfect quality control of Chrome, these quick releases do more harm then good.

by sapper2 15y ago

Unless they have the quick, silent updates of Chrome AND the (so far) perfect quality control of Chrome, these quick releases do more harm then good.

dpcan 15y ago

I JUST downloaded FF4 and now I see 5 is coming out. Version-less updates of browsers makes sense, and they should be seamlessly, silently, updated in the back-ground. This is getting crazy. I install Firefox for friends and family who I want off IE, and this actually embarrasses me a little. If I have to keep telling them to update, they will quit - or end up using REALLY OLD versions of Firefox and we'll have an IE6 situation all over again soon but with Firefox. I'm starting to install Chrome now. At least I can say that their browser will always update, and they have nothing to worry about.

jcitme 15y ago
if Firefox 17 came out 3 months ago and we are currently on Firefox 20, I don't think that's any less secure than running 3.6.5 when 3.6.7 came out...
code_duck 15y ago
Firefox has always done a good job of handling updates. It is not in the background, but it is painless and automatic once you agree to upgrade. It will never be anything like IE6 - how many people do you see using Firefox 2? or even 3.0? The upgrade to 5 isn't much different than going from 3.8 to 3.16. Mainly, they've changed their numbering scheme, so there's no reason to make a big deal about it.
thomas11 15y ago
Firefox 5 is not coming out. It's a beta. You shouldn't bother friends and family with it.
- rsoto 15y ago
  Actually, my Firefox it's advicing me to update. And I'm not on the nightly, developer or beta channel.
  - thomas11 15y ago
    Strange, mine (4.0.1) doesn't. There's something broken either in the update routine or in your Firefox. The beta is not supposed to be recommended to users of a release version.
    - rsoto 15y ago
      Yeah, I'm also very confused. While I think it's a good idea to be pushing relases more often, this is way too often. Here's the about Firefox dialog http://i.imgur.com/cDbN1.png http://i.imgur.com/cDbN1.png and the update request http://i.imgur.com/4SYRI.png http://i.imgur.com/4SYRI.png
  - zpao 15y ago
    Are you sure you're not on the beta channel? Coming from Firefox 4, that channel stuff was under the hood. If you used Firefox 4 beta, then you're probably on the beta channel (you can check in about:config looking at app.update.channel)

redemade 15y ago

seriously... WHY aren't other browser vendors adopting the chrome release strategy?

horser4dish 15y ago
There's still a market for people who want to manually upgrade. There was a comment thread on HN a few months ago about this as well (no way we'll be able to find it now, I don't remember the story), but it summarized my views very well. I like knowing what is or isn't being installed on my computer. I've got a bash script to automatically download and update to the newest Firefox, so the act of upgrading isn't a chore. But I don't want a given company, be it Google or Mozilla, to arbitrarily change what's on my computer. That's not to say I don't see the allure of automatic updates, but I just don't want them to be silent and mandatory.
- kijinbear 15y ago
  Given how configurable Firefox is, I'm sure they'll add an option to disable automatic updates even if it becomes a default feature.
- richbradshaw 15y ago
  For a web browser there is no reason not to want to use the newest build, especially while HTML5 and CSS3 are being actively implemented. Your bash script is just your own version of Mozilla's auto updater.
  - horser4dish 15y ago
    Sure there is. A while ago, while I was using the 4.0 beta, I ran into a problem: modal dialogs wouldn't work. In beta 4 they worked just fine. Beta 5, just fine. When beat 6 rolled around, they stopped working. I reverted and used that until beta 12 fixed my problem. 6-11 were useless for some of the things I used it for (example: TiddlyWiki editing) because Javascript alert() and confirm() dialogs would literally not show up. EDIT: also, the bash script is there because I install Firefox to /usr/local, and it's easier to type "update-firefox" in an already-open terminal than to reboot Firefox as root so it can modify my files. I'm aware it's redundant, but it also a) requires my active participation, so I can't miss it and b) lets me downgrade, in case of something like what happened above.