Intel might have slipped that Windows 12 is indeed coming next year | Company CFO sees benefits of a coming “Windows Refresh”::undefined

  • DeadlineX@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 months ago

    Where are you located? I don’t know any programmer who is afraid of 9. Not even in releases.

    We had a year of iterations of X.900, X.910, etc etc. None of us thought that was bad luck. And honestly we implemented some fun features to write.

    Versioning is usually done with three numbers, often separated by a period. So Major.Minor.Patch/Hotfix. So we would have X.900 for the first minor version of X.9. If (when) there is a hotfix, that becomes X.901. For a lot of other software it would be X.9.1. Either way, skipping 9 would just cause confusion. I’ve never heard of this superstition and I’ve never seen a software company skip 9 in their versioning.

    • over_clox@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      3
      ·
      edit-2
      9 months ago

      Was your software meant for internal or corporate use, or was it meant for the average everyday consumer? Internal use is one thing, but the supposed superstition regards the average end user.

      It comes off as if there’s no good reason to go for a version 4.9 system, when you might as well wait for them to iron out all the bugs and ship a polished off version 5.

      For the end user, this is especially important when you’ll have to pay for version 4.9, only to have to pay all over again for version 5. It’s like in hindsight you knew you were pissing money away on 4.9 in the first place.

      This is exactly what happened with Windows ME and Windows 2000, people just pissed their money away on ME. This is also more or less what happened with MacOS 9, people weren’t all too pleased with that either.

      Even in my own projects, if I’ve reached version numbering ending in a 9, that generally means I’m working on lots of internal changes, adding lots of features, and it is likely to have bugs. By the time I’m pretty damn sure most of the bugs are ironed out I’ll up the version number and might actually let other people use it.

      Edit: If the version numbering is for some background library that end users aren’t necessarily going to have to directly interact with or inspect, then it hardly matters, just go ahead and go sequentially.