That's what we do at my company. Customers were afraid that increasing the major number meant major changes, so they were afraid to upgrade. So we "fixed" that by keeping the major number the same, and just updating the minor number.
Nah. The problem with Firefox and Chrome isn't the high version number. It's that there isn't actually any signifier of whether it's a major release. Did big stuff change? Should I get excited about this version and try it out? For example, Firefox 57 introduced a major UI redesign, but since every version change is a "major" change, no change at all is. So people assume Firefox 57 is a lot like 56 is a lot like 55 is a lot like 43, and never take a look.
From a marketing point of view, it's stupid. From an engineering point of view, it's also stupid — there's a constant hustle to get stuff out every six weeks.
Yes, and critics aren’t “scared of high version numbers” but don’t agree to have software that is a “constant stream of changes” changing without their consent.
From the engineering perspective it’s kind of “state of the art”.
Well, software engineering is still in its infancy, and famously still rather shitty.
28
u/BlueShell7 Aug 20 '20
There's a lot of people scared of high version numbers (always hot topic under FF and Chrome releases).