Linked by Thom Holwerda on Tue 27th Sep 2011 19:45 UTC, submitted by lemur2
Mozilla & Gecko clones Mozilla has released Firefox 7. Unlike releases of Firefox 5 and Firefox 6 which were relatively minor upgrades to the browser, Firefox 7 includes a number of significant improvements, most important of which is probably the drastically reduced memory usage.
Thread beginning with comment 490956
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Biggest change...
by UltraZelda64 on Tue 27th Sep 2011 22:47 UTC in reply to "RE: Biggest change..."
UltraZelda64
Member since:
2006-12-05

No, there was a time you could look at the version number and tell if there were some major changes or not. You know, things like major compatibility and UI changes. Firefox's version number has only recently become "completely arbitrary"... since, what, Firefox 4, 5? Never mind the whole incompatible extensions mess that is brought to extreme levels with these rapid version number inflations.

Edited 2011-09-27 22:48 UTC

Reply Parent Score: 2

RE[3]: Biggest change...
by Fergy on Wed 28th Sep 2011 09:40 in reply to "RE[2]: Biggest change..."
Fergy Member since:
2006-04-10

No, there was a time you could look at the version number and tell if there were some major changes or not. You know, things like major compatibility and UI changes. Firefox's version number has only recently become "completely arbitrary"... since, what, Firefox 4, 5? Never mind the whole incompatible extensions mess that is brought to extreme levels with these rapid version number inflations.

V1.5 was more like a V1.1 - V3 was more like a V4 in comparison with V2 - V3.5 was meant to be V3.1 but became too big - V3.6 was more like a service pack to V3.5 so maybe make V3.5 a V4 and V3.6 a V4.1 - V5 should be V4.1 and V6 should be V4.2 but V7 should be V5.
Should we really use version numbers as an indication of how many changes were made? Do you think 3.6 broke less extensions than 5?

Reply Parent Score: 2

RE[3]: Biggest change...
by lemur2 on Wed 28th Sep 2011 09:46 in reply to "RE[2]: Biggest change..."
lemur2 Member since:
2007-02-17

No, there was a time you could look at the version number and tell if there were some major changes or not. You know, things like major compatibility and UI changes. Firefox's version number has only recently become "completely arbitrary"... since, what, Firefox 4, 5? Never mind the whole incompatible extensions mess that is brought to extreme levels with these rapid version number inflations.


Firefox version number has nothing to do with compatibility changes.

Mozilla has been desperately asking authors of extensions to avoid inspecting the version number to try to infer anything about compatibility.

Reply Parent Score: 3

RE[4]: Biggest change...
by vodoomoth on Wed 28th Sep 2011 11:24 in reply to "RE[3]: Biggest change..."
vodoomoth Member since:
2010-03-30


Firefox version number has nothing to do with compatibility changes.

In practice, it does for users: extensions stop working or worse, they are deactivated by FF without the warning we were given with FF 4. I've seen this with the Java Console, the .NET thingy and other plugins. Now, because we have no obvious way to get rid of those system-wide extensions, they sit there in the extensions list.

Extensions that stop working are the most annoying thing about FF.

Mozilla should have come up with a better way for extensions developers to do what they think they're doing by testing version numbers. Yeah, I know it's very easy to say in retrospect. If the stubborn devs keep doing what they are now told not do do, it's because they've been given the means to do it in the first place.

Reply Parent Score: 3

RE[3]: Biggest change...
by Soulbender on Wed 28th Sep 2011 18:26 in reply to "RE[2]: Biggest change..."
Soulbender Member since:
2005-08-18

No, there was a time you could look at the version number and tell if there were some major changes or not. You know, things like major compatibility and UI changes.


That's what release notes are for. It's not like the version number will tell you exactly what changes there are and what problems you can expect.

Never mind the whole incompatible extensions mess that is brought to extreme levels with these rapid version number inflations.


I guess the extension authors have to write better code then.

Reply Parent Score: 2

RE[4]: Biggest change...
by UltraZelda64 on Fri 30th Sep 2011 03:44 in reply to "RE[3]: Biggest change..."
UltraZelda64 Member since:
2006-12-05

That's what release notes are for. It's not like the version number will tell you exactly what changes there are and what problems you can expect.

Yes, but it's nice when the version number gives you a little hint as to what to expect.

Reply Parent Score: 2