Still, a good OS must support legacy SW. This decision whether to allow or not should be left to the customer.
That;s easily preventable if you give customers choices. They could, for example, allow writing but exclude changes to executable files.
Again, a user could easily make directories that comply with old styles.
Sure, but blanket-banning any 16-bit apps is a really bad idea. It results in lost biz opportunity for an OS maker because people will be leery of upgrades.
That's all ok as long as the OS does not blanket-ban the old stuff.
Some older CAD doesn't and there's the problem. There is a lot of custom software that is de facto irreplaceable.
Whoever buys dongled software brought the wrath upon themselves. That is one thing I never did and never will do.
Make that 30+ years :-)
I came across one piece of production equipment that would only run under Windows 3.2.
I understand one can get it to behave somewhat normal but a regular non-techie user can't get that done. Others just don't have the time to fix it. So they avoid it.