>>>>>A lot of people who remember the old days when packaged/pay once software was the only game in town are viscerally opposed to the subscription model. I'm not, as long as I get recurring value-added as well as recurring costs. But that's more difficult to evaluate in a subscription model. There's the danger that MS will make no significant improvements at all, and simply say using Windows as-is is worth $XX per renewal, if you don't like it use something else. But you can be sure they'll put full effort into locking users into the platform.
>>>>
>>>>I'd prefer a pay-as-you-go, where a gigabyte of content would be between one cent and one dollar - and for video that would include the 'pick your rez' option, so if I think it's unworthy crap I'd go with just VGA :). And they'd be surprised at how much one can be creative with the FF button or whatever they call that slider now.
>>>>
>>>>Or SAAS, where the fee would cover the features used... That would seriously reduce bloatware.
>>>
>>>What happened to Windows 9?
>>>
>>>Number 9 .... number 9 .... number 9 ....
>>
>>I heard that 9 was discarded since it would cause problems for a lot of software which only checked the first digit in the version number. So Windows 9 would be "misinterpreted" as Windows 98.
>
>My son, who used to work at Microsoft, considers that explanation nonsense, since any decent software would be checking the internal version number, not the marketing name. Makes sense to me, since I don't even know how you'd get your hands on the marketing name. Think of OS()--it gives you the internal version #.
>
>Tamar

It is my understanding that the problematic code examples were from web application scripts. Not sure if internal OS version number is available in such cases.
I recall running into similar types of shortcomings while working in VBscript when trying to get the current time in terms of Universal Time rather than the local timezone (which may or may not have daylight saving offset applied)..