- Oct 29, 2000
They could mitigate any compatibility breaking side effects from doing the right thing by sandboxing and internally using some sort of compatibility mode utilizing VM's or something like that. They already do stuff like that to allow the running of older titles and software in Windows Vista and beyond. If the mostly volunteer comparatively small WINE project can get a workaround going for a majority of things, I'm sure Microsoft with their army of software engineers can as well.So, how do you suggest they do that well also maintaining backwards compatibility spanning 30 or so years?
In the end, most software will still work, and the stuff that doesn't the vendors will just be forced to patch.
You can't let really bad design stick around forever just because you are afraid of breaking compatibility. If that were the case we wouldn't have a number of features we depend upon today, including UAC, virtalized RAM addressing, etc. etc. etc.