Live data from Hacker News

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

developer.apple.com

231–240 of 450 posts

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

#231

Earlier quoted context omitted.

Interestingly, I feel the opposite: Homebrew acts much more like a binary distribution service than a package manager.

Those don't seem to be opposing things - you expect your package distribution tool to be effectively curl and tarballs, the other person expects more complex behavior options and dislikes the absence of them.

(I use MacPorts)

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

#232
post #186

Earlier quoted context omitted.

> Windows users have had no choice but to do that for decades. You're saying this like it's a good thing.

It's not a good thing or a bad thing. I'm saying it's not a thing at all. If someone decides they want to run a custom ruby or python script the least difficult aspect of that decision is installing the interpreter. For example, I was dealing with someone yesterday who decided they wanted to learn how to write apps for Android. Without even seeing a single line of code (or even knowing which language they would have…

Lots of people on just this thread, who have far more than a glancing interest, have expressed their disagreement with this exact idea.

The hardest part for lots of people in learning to program is getting over the idea that programming is for Special People, or possibly Wizards, who know lots of incantations which are beyond mere mortals. Please stop trying to convince them they're right.

Source: I've taught lots of marketing people, admins, call center techs, etc to program in PowerShell or system Python.

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

#233

Earlier quoted context omitted.

Again the word "serious" is there telling me people are absolutely aloof to the kinds of new developers there are and what it's like to be a non programmer.

What newbie will start with Python 2.7 at this point in time? Most books and tutorials are updated for Python 3. The default Python 2.7 interpreter from macOS is useless for newbies, it does more harm than good by confusing them.

The young, bored but smart kid in an elementary or middle school tinkering with her computer and finding something to do. She doesn't need a book or a tutorial to tell her the "right" way. She experiments, only guided by her curiosity.

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

#234

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.

Python and pip just being there is a huge advantage for newbies. I really think that part of programming is constantly ignored because all the decision-makers are not newbies.

Not only pip is not provided, but virtualenv neither.

The alternatuve to the current decision is for apple to assign people to keep updating python and provide previous versions as packages like linux distrib does. But it has never been the way they do business.

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

#235
post #132
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…

I think you’re overthinking this. The vast majority of Ruby/Python programmers have been installing their own copies themselves, because Apple was pretty slow in updating them (Ruby is usually a few minor releases behind, Python is still 2.7 IIRC). People will just keep doing that, and nothing will change. They may or may not be moving off Unix, but this isn’t evidence of that.

Right, I think most developers know that it's a bad idea to mess with the old, unmaintained system versions of Python, Ruby, or Perl. Almost everyone I know uses Homebrew to install the bleeding edge versions separately, and that will save you a world of pain.

For Python folks, just install pyenv/pipenv and you can easily maintain `system` (Python), Python2.7x, Python3.7.3, &c as separate environments. For Ruby people it's rbenv.

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

#236
post #147

Earlier quoted context omitted.

> Ruby on Windows is a nightmare. The same stuff with Node.

Not sure why? Yeah there were times with damn node-gym not compiling for whatever reason. But nowadays things run pretty smooth.

Besides paths, Http_proxy settings on enterprise networks is a major pita.

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

#237

Earlier quoted context omitted.

They've got enough market clout now that people will port Ruby/Python/Perl to a non-Unix macOS, just as they port them to Microsoft Windows. Ruby on Windows is a nightmare. To be specific, Ruby itself (the core language and core libraries) are pretty good on Windows. Great choice for a scripting language, or whatever else you want to do. But libraries like ActiveRecord, Rails and their myriad dependencies are very ve…

The funny thing is I have been a rails dev for years and didn't even know it didn't work on windows because I have never tried and don't know any dev ever using windows.

That just proves you live in a bubble :) I never got into RoR because it sucked so much on windows and every single tutorial was OSX focused. I just sticked to alternatives that worked.

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

#238
post #228

Earlier quoted context omitted.

Yes

I'm not sure why you are getting downvoted. I'd not like it if Apple will opinion-ate and make any package manager a default. Package managers are for software developers. They are comfortable installing them on their own.

I expect he’s getting downvoted because he doesn’t offer any reasoning (or substance at all) along with his opinion.

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

#239

Earlier quoted context omitted.

Yeah I don't get the trend to install it with brew since it's so easy to use the official installer.

Package managers will keep your Python up-to-date automatically.

Sure but it's very rare to update python on the desktop (not on the server). Installing a new version in parallel is common, but once you get a 3.x rolling, you seldom have the need for a 3.x.y unless you encounter a bug or are very security conscious.

On the other hand, installing xcode is really a pain.

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

#240

Earlier quoted context omitted.

Python and pip just being there is a huge advantage for newbies. I really think that part of programming is constantly ignored because all the decision-makers are not newbies.

It's honestly terrible for newbies. If they try to use it, there's no pip included. So then they easy_install all their libraries which installs things into different places than most python devs will be used to. Or they easy_install pip first. But even still, everything is installing to system paths, so when they try to install things it fails with permission errors. They find a stack overflow post that says just "s…

you can always brew uninstall and reinstall later if you need a different version

That is the wrong way to do it. Just install pyenv/pipenv to manage different Python versions. It's dead simple to maintain system Python, Python 2.7x, and Python3.7.3 that way.

Post reply on HN