It was just my thought it could be Win 11, but MS could just stop at 10 and just provide updates.
engine... thanks. They'll then call the next one 10+, to be followed by 10++plus, etc? ;)
The dilemma, I think, is that if there's a different architecture to the hardware, that will naturally cause a fork in the software, with probably no way of keeping the OS backwardly compatible. In my prior fields of photography and motion pictures, with video kind of sandwiched in there... there came to be so many forks, first in analogue standards, then in digital standards... so many forks that folks began eating with their hands.
Each standard required different machinery, training, work-flow, and infrastructure.
In some "stardards", there are so many options that no one ever implemented them all in one machine, so compatibility couldnt be tested. I remember the first time I had video "authored" to a DVD... not a machine conversion, which looks crappy, but instead an artful and expensive conversion... that before the studio made release copies, they ushered me into a "machine room", literally stacked to the ceiling with DVD players, and invited me to spend as long as I'd like checking it out. There was no way that the company could economically guarantee their product would work on all hardware. And it was often the expensive machinery that gave the most problems.
With software, Adobe couldn't keep up with the "codec" variants on different cameras and video systems, and decided on a subscription model for its software, which shifted the cost of "progress" to the customer.
I certainly hope this doesn't happen in computing... more so than there has been... because there's truly no end to it. Each version becomes a beta version for the next version, and they
never get things working right. It's a bottomless pit.