3 ms·
It’s never a good time to take a breaking change. Microsoft has had a pretty extreme view of what’s “compatible”, including what seems to be a desire to not bre
by alkonaut 8y ago
It’s never a good time to take a breaking change. Microsoft has had a pretty extreme view of what’s “compatible”, including what seems to be a desire to not break existing applications that rely on undocumented or buggy behavior.
I’d want to argue that removing bugs and fixing things like this should just be done with a reasonable notice period and if some aging system in the basement of a fortune500 company blows up then I’m sure that can be solved too.
This said, I find the 70s smell more present and annoying in a Unix terminal than in Windows explorer. All the big OS’es are dinosaurs and it will show up here and there.
- jacob019 8y agoThere's no need to break the old stuff. Applications can signal compatibility level so that new applications need not support legacy cruft.
- oneeyedpigeon 8y agoSo your OS is always a bloated superset of its entire history?
- jacob019 8y agoOld compatibility levels can be deprecated at some point, this would qualify.
- anticensor 8y agoWindows already does it. The problem being there is no manifestation mechanism in MS-DOS executable format. No, it is harder to work with such a system.