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

Post by comex » Thu, Jun 06, 2019, 2:41 AM UTC

ihuman wrote: post #12

olliej wrote: 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?

Post by brianwawok » Thu, Jun 06, 2019, 2:42 AM UTC

dwaite wrote: post #27

AceJohnny2 wrote: post #17

Earlier quoted context omitted.

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.

> Does anyone actually use Docker on Mac? I use it extensively. It is a desktop product however; it you aren't expected to put a swarm of MacBook pros into production.

Post by george_perez » Thu, Jun 06, 2019, 2:46 AM UTC

drivingmenuts wrote: post #83

cprayingmantis wrote: post #66

Earlier quoted context omitted.

The down side to that is that ruby is currently required to install Homebrew.

There will be a .pkg for that, if there isn't already.

Post by Wowfunhappy » Thu, Jun 06, 2019, 2:47 AM UTC

drivingmenuts wrote: post #82

ken wrote: post #76

Not surprising at all. It's become clear that what they've been doing with iOS all along is bootstrapping a new operating system. They started with Unix, not because Unix was optimal for what they wanted to do, but it's what they had and it worked well enough. Copland and Taligent and the rest failed because of Second-System Effect, which Apple was smart enough to avoid. (As RMS wrote in 1983, "Unix is not my ideal s…

A different solution, and possibly better, would be to run Unix/Linux in a VM rather than worrying about it being native in the system. If I'm not mistaken, current best practice is to somewhat isolate third-party developer software anyway, using homebrew, a VM or other solutions (not sure about Docker - don't use it). I can see where it would be an issue with developing for MacOS or iOS, but third-party web developm…

Post by bla3 » Thu, Jun 06, 2019, 2:53 AM UTC

olliej wrote: post #68

bla3 wrote: post #58

I don't understand why everyone is so excited about this. I don't like using brew. I use a Mac because things just work. It was annoying that the system versions were old, but most of the time they were still workable. To me, this is another (admittedly small) thing I liked about the Mac that's going away.

The problem is accruing security flaws (increasingly difficulty to back port fixes), and also the problems that come up when you install a different version (lots of Software just assumes it can use the same system python, which causes issues when it isn’t the archaic version).