I hope you do understand that it would not damaging compatibility with 95-98, but with windows 8. The class of programs that this is for runs fine on Windows 8, because they are not executing legacy code for 95-98. But the check for 95-98 would return true for windows 9. So the legacy code will be executed, probably breaking stuff because the API has changed a lot.

And as for some evidence this is the case: https://searchcode.com/?q=if%28version%2Cstartswith%28%22win...

> Programmers will check the kernel version, not the "friendly" consumer-facing string.

Cute. New to the profession?

Chew on this:

http://www.reddit.com/r/technology/comments/2hwlrk/new_windo...

> Programmers will check the kernel version, not the "friendly" consumer-facing string.

I wish that were true, and it may be if you're dealing with competent developers, but I've seen code that does exactly that in the wild!

Here's some evidence to support the inference regarding the out of order naming:

https://searchcode.com/?q=if%28version%2Cstartswith%28%22win...

Interesting that you would call my claim "highly improbable" because I didn't cite any sources and in the same breath, make a claim without any sources.

"Unverified"? Sure. "Highly improbable"? You don't know that any better than I do.