3 ms·
They could remove it in a new version of windows, that crusty POS system is going to be doing a lot of testing before they upgrade the version of windows it's r
by flukus 9y ago
They could remove it in a new version of windows, that crusty POS system is going to be doing a lot of testing before they upgrade the version of windows it's running on. Even more likely is that they'll never upgrade from whatever ancient version they're using so it won't affect anyone.
I think they just keep it because it feeds into the backwards compatibility myth that MS has built up.
- colejohnson66 9y agoOr they could just create a registry flag that enables the backwards compatible behavior. Then all default installs don't have the "bug", while those that need it can enable it.
- captainmuon 9y agoThey could probably make the new behavior opt-in in the application manifest. Without a manifest, you'll see pre-XP common controls, and GetVersion will return an old version, so every modern application has it anyway.