4 ms·

If Firefox hadn't gone on a version roller coasters ride I'd still be using it. At least they pull versions that need more attention. But, FF 16!?!?! 16!!!? Huh

If Firefox hadn't gone on a version roller coasters ride I'd still be using it. At least they pull versions that need more attention. But, FF 16!?!?! 16!!!? Huh? . . . you do know Chrome's at version 22 and version 24 is in dev release, right? Knock FF for the more disruptive update process, and for breaking plugins in earlier releases, sure. But (AFAIK) the plugin interfaces have been stable for quite some time now, and Firefox 15 introduced true silent updates. They seem to have fixed the pain points in their rapid release schedule. If you use Chrome, however, you cannot knock them for iterating more quickly; Chrome's in the same boat.

jebblue 14y ago
>> If you use Chrome, however, you cannot knock them for iterating more quickly; Chrome's in the same boat. My Chrome plugins don't break. They can change the version every day for all I care just don't break my plugins, extensions.
- rpearl 14y ago
  Guess what? That happens with Firefox too.
- timdorr 14y ago
  You know they're going to break old extensions in a year, right? http://developer.chrome.com/extensions/manifestVersion.html http://developer.chrome.com/extensions/manifestVersion.html
  - jebblue 14y ago
    Any developer who can't upgrade their extension with that much notice and with that clear of a specification and I don't want to use their extension any more if it breaks.
- ryannielsen 14y ago
  And, as I said, Firefox no longer breaks plugins. Yes, they did. Yes, that was bad. They claimed, and I believe, that was necessary, but today their plugin interfaces are stable and have been stable for quite some time. Also, believe me, Chrome is not without its bugs or regressions. Rapid iteration means things will break more often, by its very nature. Hence my statement: you can't knock Firefox for rapid releases if you've moved to Chrome. You're in the same damn boat.

jebblue 14y ago

>> If you use Chrome, however, you cannot knock them for iterating more quickly; Chrome's in the same boat. My Chrome plugins don't break. They can change the version every day for all I care just don't break my plugins, extensions.

rpearl 14y ago
Guess what? That happens with Firefox too.
timdorr 14y ago
You know they're going to break old extensions in a year, right? http://developer.chrome.com/extensions/manifestVersion.html http://developer.chrome.com/extensions/manifestVersion.html
- jebblue 14y ago
  Any developer who can't upgrade their extension with that much notice and with that clear of a specification and I don't want to use their extension any more if it breaks.
ryannielsen 14y ago
And, as I said, Firefox no longer breaks plugins. Yes, they did. Yes, that was bad. They claimed, and I believe, that was necessary, but today their plugin interfaces are stable and have been stable for quite some time. Also, believe me, Chrome is not without its bugs or regressions. Rapid iteration means things will break more often, by its very nature. Hence my statement: you can't knock Firefox for rapid releases if you've moved to Chrome. You're in the same damn boat.