3 ms·

I guess the average person assumes that a higher version number implies a 'better' (define your own interpretation) product. Seems Google is joining that partic

by BjornW 16y ago

I guess the average person assumes that a higher version number implies a 'better' (define your own interpretation) product. Seems Google is joining that particular use of version numbers as marketing. And to be honest, to some degree I can completely understand this. Imagine having to explain why Internet Explorer 6 is not a better product than Firefox 3.... As a developer I always find it hard versioning my work. Why do I consider it to be a 0.8 and not 1.0? Why would you consider it 1.0 and not 0.8? I try to stick to the following rule of thumb: a.b.c a) Major changes or multiple big new features b) Medium changes, maybe one or twee new small features c) Improvements I'm curious as to what 'system' other people use to determine their software's version numbering.

civilian 16y ago
"Seems Google is joining that particular use of version numbers as marketing." I disagree. Sure they have higher numbers, but they're also not making a big deal about it.
ShabbyDoo 16y ago
"Seems Google is joining that particular use of version numbers as marketing." Perhaps. But, if this is really their strategy, they're doing a terrible job of it. If they really are thinking this way, wouldn't they be much louder about it? I suspect that products for which major releases are trumpeted loudly by marketing organizations (think IE9) elicit two kinds of reactions: (1) "Wow, I have to download that NOW!" and (2) "New things are scary, so I will avoid upgrading." Reaction #2 is what has caused IE6 to die such an agonizingly slow death. Grandmas probably thought it scary to upgrade, and IT managers certainly have been burned in the past by "major" software upgrades. The web browser experience improves only when developers believe the lowest common denominator browser feature set of their user base has shifted upward and they can therefore drop support for older stuff. It doesn't matter so much now quickly IE9 is adopted compared to how quickly IE6 (and 7, etc.) go away. Perhaps by positioning newer versions of Chrome as just a normal course of change (much like Microsoft security patches), Google hopes to help the laggards hurry up.

by BjornW 16y ago

civilian 16y ago

"Seems Google is joining that particular use of version numbers as marketing." I disagree. Sure they have higher numbers, but they're also not making a big deal about it.

ShabbyDoo 16y ago

"Seems Google is joining that particular use of version numbers as marketing." Perhaps. But, if this is really their strategy, they're doing a terrible job of it. If they really are thinking this way, wouldn't they be much louder about it? I suspect that products for which major releases are trumpeted loudly by marketing organizations (think IE9) elicit two kinds of reactions: (1) "Wow, I have to download that NOW!" and (2) "New things are scary, so I will avoid upgrading." Reaction #2 is what has caused IE6 to die such an agonizingly slow death. Grandmas probably thought it scary to upgrade, and IT managers certainly have been burned in the past by "major" software upgrades. The web browser experience improves only when developers believe the lowest common denominator browser feature set of their user base has shifted upward and they can therefore drop support for older stuff. It doesn't matter so much now quickly IE9 is adopted compared to how quickly IE6 (and 7, etc.) go away. Perhaps by positioning newer versions of Chrome as just a normal course of change (much like Microsoft security patches), Google hopes to help the laggards hurry up.