3 ms·
Microsoft's commitment to backwards compatibility is definitely one of the strengths of the Windows platform. On the flipside, it's also at the root at the insa
by pdpi 3y ago
Microsoft's commitment to backwards compatibility is definitely one of the strengths of the Windows platform. On the flipside, it's also at the root at the insanity that is the forbidden word list in MS Teams channel names.
https://learn.microsoft.com/en-us/microsoftteams/limits-specifications-teams#channel-names https://learn.microsoft.com/en-us/microsoftteams/limits-spec...
- vb6sp6 3y ago[dead]
- deleted 3y ago[deleted]
- yjftsjthsd-h 3y agoI wonder if they could have mitigated that by leaning more heavily on the ability to have multiple personalities running on top of the kernel. So for instance, you could run a program from 1996 on the "Windows 95" subsystem and get better compatibility, but Teams could run on the "Windows 11" subsystem that treats CON as just another file name. Of course, there might be a problem if programs at different compatibility levels interact with the same files, but there's actually precedent for dealing with that kind of thing quasi-transparently, or perhaps I should say QUASI-~1.