| Not to put too fine a point on it, but those examples don't pass muster. - If you're not using .NET, the CLR doesn't affect you, and although Microsoft has done well with ,NET, I wouldn't necessarily expect Apple to make Redmond's job easier. - Java is much the same boat, and is perhaps in even worse shape as it used to be included by default in macOS releases but now isn't. Read: security nightmare. - From 10.16 on, scripting languages also aren't included by default. This seems less adversarial than the situation with Java, but for things like Homebrew, it's a stumbling block they will need to overcome. https://discourse.brew.sh/t/mac-os-deprecating-system-script... |
Are you predicting that Apple will disallow all scripting language runtimes and all VM based development environments? So if these same predictions have been wrong for over a decade - and still aren’t happening with 10.13, exactly when will this happen?
As far as Apple not including (outdated) versions of various scripting languages or Java - neither does Microsoft. That hasn’t been a major impediment to adoption.