4 ms·
If you explicitly manage your scripting language versions, none of what you’ve described is a problem. Instead, your post reads from a perspective of fear, unce
by daviddever23box 7y ago
If you explicitly manage your scripting language versions, none of what you’ve described is a problem. Instead, your post reads from a perspective of fear, uncertainty and doubt that doesn’t line up with developer experiences.
As for iOS, it is not the same as macOS and should be considered separately. I’m not sure why you’ve equated the two (different use cases), but maybe you are genuinely (and unnecessarily) worried.
- mschuster91 7y agoAlone removing perl would massively suck because many shellscript installers depend on some form of perl being present on the system, partially to avoid the differences between GNU/Linux userland (sed!) and OS X userland.
- microtherion 7y agoperl is probably a good demonstration of the problems of bundling scripting languages, as macOS ships with two different versions of perl 5.
- wahern 7y agoThe fear is unification of iOS and macOS, which Apple has hinted at occasionally. macOS doesn't need to disappear completely for many fears to be realized. The more application APIs are unified, for example, the more pressure there becomes for macOS to deprecate and let stagnate its POSIX interfaces. And you don't need the POSIX interfaces to disappear completely for the environment to cease being targetable by most open source projects, especially command-line projects. Windows has a significant number of POSIX APIs stemming from Windows NT 4.0 POSIX compliance, but it's just not a practical Unix target based on that subset alone.
- toxik 7y agoI disagree that anything hints at unification. They have literally said outright that they want one OS for each platform, hence why iPadOS was born proper. The aim is to reach feature parity across their three systems though, so you have a point.