Some Clarification and Musings
tylerdowner.wordpress.com
tylerdowner.wordpress.com
[1]: http://tylerdowner.wordpress.com/2011/08/29/even-more-clarif...
Now realize that's just semantics.
For the record I am a diehard firefox user, 6000 bugs or not.
This doesn’t matter. At the end of the day it’s about severity. If Firefox ships with 31,992 critical end-user visible bugs then it’ll be rightly panned. It hasn’t been, therefore the large majority of the issues aren’t that severe, therefore they can be dealt with at a slower pace.
[+] https://bugzilla.mozilla.org/buglist.cgi?list_id=1199753&...
http://catb.org/~esr/writings/homesteading/cathedral-bazaar/...
I guess it's a matter of perspective (and of which HN headlines attract your attention :) )
For Windows, on the otherhand, I love Firefox so much. I do fine it's performance and UI so much better. Chrome sucks with lots of tabs open and the UI just bores me.
Now, the problem mentioned in the OA is quite real. Some of the processes of Mozilla have not scaled up yet. I suppose that they will.
There is a three part version number for a reason, use it.
Firefox 5 should have been 4.5 and 6 should have been 4.6
If you want to release every other month to imply there are improvements, go for it - just don't imply there are major changes for "political" reasons.
Maybe all the big guys are doing it wrong, but with every new Firefox release since 3.6.x I've had problems getting Firebug and 1Password working. And I have a hard time faulting them for not being able to keep up. And I've just had to give up on using the ElasticFox add-on at all.
Also, these days Mozilla has the "Add-On SDK" which provides an abstraction around the core Gecko and Firefox APIs that is more Chrome-like - more limited than what a traditional Firefox extension can do, but guaranteed to stay compatible for a long time into the future.
To me, the reasoning behind the change in version is pretty clear. Especially looking at the disaster that was IE6. As soon as there is any support for old versions some IT department somewhere will immediately decide it's time to freeze their version. Moving forward after making a freeze like this becomes very difficult (that has been my experience). This presents two options 1) It's their own problem and move on or 2) Continue to patch old versions. The issue with patching old versions is bad IT decisions end up costing Mozilla time. Meanwhile chrome just continues chugging along at full speed only supporting current.
The current linux distro versioning and support structure seems to map well to this problem. Ubuntu, for instance, has LTS versions that IT can stick with and are patched for X many years.
Windows users update their anti-virus software and definitions in near real-time. Operating Systems update near real-time... why not browsers. I now use chrome most of the time and I am (surprisingly) happy with their versioning. I was a naysayer when they first started too.
In all seriousness - Firefox version 25 in two years, think about that and how no-one is going to take major version numbers for real anymore.
If they insist on this, I'd rather have a YEAR.MONTH version number. Firefox Version 2012.4
They're going to stop having any version numbers.