Earlier quoted context omitted.
There’s also no reason that the public facing name has to be the same as the internal name. They could have called it Windows 9 and internally reported it as anything in the apis. Its basically standard in software to do this when the actual name for something comes out near the end or changes often so you don’t have to update all the code to reference the new name.
> There’s also no reason that the public facing name has to be the same as the internal name. They could have called it Windows 9 and internally reported it as anything in the apis. This is what they were doing at the time anyway. Windows 7 was 6.1, Windows 8 was 6.2, Windows 8.1 was 6.3.
And still to this day, where Windows 11 is for instance version 10.0.26100