3 ms·

Eh? The version number changed. MSFT just changed to something not completely predictable in advance. Or am I missing your point?

• bonzini 9y ago
  They _had_ to change it to "10" because there was existing code in the wild that misbehaved for a hypothetical Windows 9.
  • _jal 9y ago
    I still don't get it; either I'm remarkably dense today, or there's a disconnect. I wrote: > anyone who expects it not to change And you appear to be using an example of a version-change curiosity as a counterexample. It is not a counterexample, because the version number in question changed from 8 to 10. In my original formulation, anyone who claimed to worry that the number would stay 8 forever was being an idiot or being obtuse. I think that holds up. It was not part of my comment, but someone who expected it to be 9 would not be an idiot or obtuse, because that would have been a reasonable guess, absent additional information. They were expecting it to change but were surprised by an exceptional circumstance. But this is getting a bit silly; there may be someone out there who thinks version numbers should be immutable across versions, but I bet they're pretty lonely. It was an example picked up while making a wider point.