Earlier quoted context omitted.
Yes, basically this news means "Ruby, python and Perl may not be preinstallled, install them yourself". It's not a big deal for users of Homebrew or other package managers.
It’s a big deal for Homebrew, which is written in Ruby and uses the version shipped with macOS to install itself.
Apple to Deprecate Scripting Languages in Future Versions of macOS
41–50 of 67 posts
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#42It’s not really UNIX anymore.
POSIX defines what Unix is, and there's no Python/Ruby/Perl here: https://shellhaters.org https://pubs.opengroup.org/onlinepubs/9699919799/
And The Open Group doesn't use POSIX, it uses the Single Unix Specification.
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#43Good internally for Apple to stop relying on them.
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#44Its like using the default web browser to download the "browser of your choice".
There is the issue that apple usually "quarantines" executable downloads ("You downloaded this from X, do you really want to run) and these scripts do an end run around that. will apple be forcing a download of a signed package dng that installs macports or brew..?
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#45Earlier quoted context omitted.
To do so would run counter to the "Mac's don't get viruses/malware" mythology. There's been a persistent "That's only a PC thing" for a long time. Fairly sure it was even referenced in Apple's own advertising during the "I'm a Mac, I'm a PC" phase.
Apple still advertises their operating systems as "Secure By Design". With the latest news about iOS zerodays in the wild for years, we know this isn't true. Do a google search for "Secure By Design" site:apple.com to see where they use this term for both iOS and OSX. Someday, someone will win in court over this.
Done well it should substantially reduce the number and severity of security issues. To back up your claim from a numbers standpoint you’d have to quantify the number and severity of security issues in Apple OSs vs comparable OSs that aren’t “Secure by Design”. That’s obviously problematic in a few ways. You could also analyze the design of the OS for security flaws. Though again, finding that the design isn’t perfect isn’t enough. You’d need to show how the design disregards security. A proper analysis should acknowledge history, BTW.
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#46Earlier quoted context omitted.
Whoa, I’ve been using Mac for almost a decade and I never knew it shipped with perl!
Most Unix systems do. Apple just does a terrible job of keeping scripting runtimes up to date.
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#47scripts are just text files that can do a great deal when executed by the scripting language runtime Microsoft have done a lot in Windows 10 to counter PowerShell malware https://blogs.technet.microsoft.com/poshchap/2015/10/16/secu... https://www.microsoft.com/security/blog/2017/12/04/windows-d... It’s not foolproof but it copes with many common attacks. It’s surprising Apple hasn’t taken this approach.
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#48Also AppleScript?
Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#49Re: Apple to Deprecate Scripting Languages in Future Versions of macOS
#50I think its going to cause problems for developers if they completely remove them. As people won't be able to run the script to install the things that give them up to date scripts. Its like using the default web browser to download the "browser of your choice". There is the issue that apple usually "quarantines" executable downloads ("You downloaded this from X, do you really want to run) and these scripts do an end…