Live data from Hacker News

Apple to Deprecate Scripting Languages in Future Versions of macOS

tidbits.com

41–50 of 67 posts

Re: Apple to Deprecate Scripting Languages in Future Versions of macOS

#41
post #6
post #4

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.

They already bring in ruby for installs on ancient MacOS, they'll just do the same here when the time comes.

https://twitter.com/mistydemeo/status/1135934513173811200

Re: Apple to Deprecate Scripting Languages in Future Versions of macOS

#42
post #28

It’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/

No, the The Open Group, which owns the trademark on the name "Unix", defines what Unix is, and that group defines macOS as Unix. It also defines z/OS as Unix and does not define any of the Open Source BSDs as Unix, which means FreeBSD, OpenBSD, and NetBSD are not Unix and are, at most, Unix-like. OTOH, the Inspur K-UX Linux distribution is Unix.

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

#44
I 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 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

#45

Earlier 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.

Designing for security doesn’t guarantee no security issues.

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

#46
post #20
post #17

Earlier 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.

Everything seems to be frozen in time at just before a project changed to GPL 3

Re: Apple to Deprecate Scripting Languages in Future Versions of macOS

#47

scripts 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.

PowerShell has bent over backwards from day one to avoid being a vector for malware. You can't invoke a .ps1 file from ShellExecute (that is to say, by double-clicking it), in its default configuration Windows Server won't run an unsigned script and client won't run a script at all, and there are fine-grained settings to control execution policy and language mode across your enterprise. That's not to say it doesn't get used for malware, but in its default state you have to actually be running arbitrary code in some other language before you can jump to PowerShell. (When PowerShell was being designed, it was right after the infamous security push in Windows, and they knew that if they shipped a new scripting language you could double-click from an email, they'd be crucified for it.)

Re: Apple to Deprecate Scripting Languages in Future Versions of macOS

#50

I 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…

They won't get rid of zsh, which they've just adopted as the default shell going forward. Macports and homebrew can bootstrap with a shell script.
Post reply on HN