Live data from Hacker News

macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

developer.apple.com

11–20 of 450 posts

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#11

This has been a topic brought up internally at Apple many times over the past decade. Glad to see it finally moving forward. Although I see the benefits to having a system-version of these packages.. if you're doing anything serious for production then the environment should be containerized.

Does OSX offer reasonable container technology? chroot?

macOS has a native hypervisor framework, Docker and xhyve uses it.

https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#12
post #10
post #5

Does this include AppleScript and the Javascript runtime for AppleScripts? They reference Script Editor in the section above, so I'm assuming they're safe. Also, what's the best way to install homebrew if you don't have a system-level ruby? The current installer is a ruby script. Is it possible to get some sort of ruby-bootstrap that can install homebrew and a homebrewed ruby?

No - the problem with the misc other interpreters is that they don’t provide sufficient binary stability for Apple to simply include the newest one in every update (which I suspect they would happily do). They’re not removing the commandline (although moving to zsh? :-/), or banning interpreters. They’re just not including them built into the os anymore. As for the AppleScript and JavaScript questions: Apple makes th…

I think you read more into my question than what I meant. I was asking literally about the best way to install it was without a system level ruby. Once you have homebrew, you can install ruby; but what about before that? Download and install ruby from ruby-lang.org, install homebrew and a brewed ruby, then uninstall the one from ruby-lang.org?

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#14
post #3

Seems like a good move. Less cruft and don't have to deal with managing versions between the one you want and the one already on the system.

I can't recall using the built-in version in ages, it is pretty much always homebrew before you even start. So I think this is a great move.

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#15
Fucking finally! Between this and deprecating Bash [1], I'm glad macOS is dropping all these obsolete packages it's been including (Emacs soon?). Their antiquity mean they're more of a hindrance to proper development than help.

Now, if they'd officially endorse one open-source packaging solution as an alternative, I'd be fully satisfied.

[1] https://news.ycombinator.com/item?id=20090193

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#16
post #3

Seems like a good move. Less cruft and don't have to deal with managing versions between the one you want and the one already on the system.

I can't recall using the built-in version in ages, it is pretty much always homebrew before you even start. So I think this is a great move.

How is homebrew installed?

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#17
post #11

Earlier quoted context omitted.

Does OSX offer reasonable container technology? chroot?

macOS has a native hypervisor framework, Docker and xhyve uses it. https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit

In other words, nothing serious.

Does anyone actually use Docker on Mac?

Xhyve is more of a proof-of-concept than a production-ready tool.

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#18
post #12
post #10

Earlier quoted context omitted.

No - the problem with the misc other interpreters is that they don’t provide sufficient binary stability for Apple to simply include the newest one in every update (which I suspect they would happily do). They’re not removing the commandline (although moving to zsh? :-/), or banning interpreters. They’re just not including them built into the os anymore. As for the AppleScript and JavaScript questions: Apple makes th…

I think you read more into my question than what I meant. I was asking literally about the best way to install it was without a system level ruby. Once you have homebrew, you can install ruby; but what about before that? Download and install ruby from ruby-lang.org, install homebrew and a brewed ruby, then uninstall the one from ruby-lang.org?

I’m guessing home brew will end up creating a packaged installer than includes a home brew upgradable ruby

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#19
post #16

Earlier quoted context omitted.

I can't recall using the built-in version in ages, it is pretty much always homebrew before you even start. So I think this is a great move.

How is homebrew installed?

https://brew.sh

Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

#20
post #12
post #10

Earlier quoted context omitted.

No - the problem with the misc other interpreters is that they don’t provide sufficient binary stability for Apple to simply include the newest one in every update (which I suspect they would happily do). They’re not removing the commandline (although moving to zsh? :-/), or banning interpreters. They’re just not including them built into the os anymore. As for the AppleScript and JavaScript questions: Apple makes th…

I think you read more into my question than what I meant. I was asking literally about the best way to install it was without a system level ruby. Once you have homebrew, you can install ruby; but what about before that? Download and install ruby from ruby-lang.org, install homebrew and a brewed ruby, then uninstall the one from ruby-lang.org?

[deleted]
Post reply on HN