Live data from Hacker News

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

developer.apple.com

331–340 of 450 posts

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

#331
post #220
post #136

Earlier quoted context omitted.

As I understood it, scripting languages will still be available to the user, they just won’t have ancient versions preinstalled. Of course that also means you can’t rely on them being installed at all as a developer. Which means you should start bundling the stuff you need to run your app, and, they’d like you not to use the same ancient batteries as they have previously made available, because, well they are ancient…

Ok, I guess it's worded vaguely enough to allow for the possibility of optional installation ("by default"), even though they don't outright promise that they'll offer a way to install it. (I interpreted it in the same way as "macOS doesn't include Photoshop by default".) Having it come from the app store doesn't seem totally appropriate since it would need to do more than dump a bundle into /Applications, like makin…

I suspect they plan to distribute the scripting languages the same way they currently handle the command line developer tools package, where the OS offers to download and install the package the first time you try to run one of those tools.

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

#332
post #268

Sounds like these runtimes will still be available via a separate download, similar to how Git and other CLI tools download when you first try to use them. Not a big deal. Makes it easier for folks who want newer versions and avoid any strange behavior with coexisting with the built-in runtimes.

Yeah, one of my pet peeves is logging in to a new system and being like "Which version of Python am I going to have to try and avoid invoking today".

Nothing quite like a bit of snake dodging to start your day.

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

#333
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…

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…

> Ruby on Windows is a nightmare.

It hurts when I do this ... [punches self in face] ...

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

#334
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…

>> (As RMS wrote in 1983, "Unix is not my ideal system, but it is not too bad. The essential features of Unix seem to be good ones, and I think I can fill in what Unix lacks without spoiling them. And a system compatible with Unix would be convenient for many other people to adopt.") I have a historical question and I wonder if anyone in this thread has the answer: why did RMS (and, presumably, by then his cycle) had…

There is GNU/HURD that was supposed to be the kernel. However, its development hit roadblock when microkernel design ended up extremely difficult to debug. Sometimes you can't predict real complexity from the architectural drawing board and prevailing hype in academia, pointing to microkernels as the future at that time. Linus just wanted to implement his own, simple UNIX kernel, based off proven principles, without doing original kernel research.

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

#335
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…

>> (As RMS wrote in 1983, "Unix is not my ideal system, but it is not too bad. The essential features of Unix seem to be good ones, and I think I can fill in what Unix lacks without spoiling them. And a system compatible with Unix would be convenient for many other people to adopt.") I have a historical question and I wonder if anyone in this thread has the answer: why did RMS (and, presumably, by then his cycle) had…

https://en.wikipedia.org/wiki/GNU_Hurd

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

#336
post #210

Earlier quoted context omitted.

You can use / on Windows in node perfectly, and Windows node now installs required devtools for native modules at the end of the process. It's pretty easy these days.

You can use it, yep, but devtools aren't enough. You'll meet a lot of issues sooner or later. Windows is second-class citizen for Node, Linux or macOS are much better - just share my experience.

Personally I moved to Windows about 2 years ago, have been developing node all day during that time and deploying on Linux. It's been great since about node 8. What have your issues been?

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

#337
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…

>> (As RMS wrote in 1983, "Unix is not my ideal system, but it is not too bad. The essential features of Unix seem to be good ones, and I think I can fill in what Unix lacks without spoiling them. And a system compatible with Unix would be convenient for many other people to adopt.") I have a historical question and I wonder if anyone in this thread has the answer: why did RMS (and, presumably, by then his cycle) had…

They tried it's GNU Hurd.

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

#338
post #317
post #241

Earlier quoted context omitted.

Open Terminal $ echo "hello" seems pretty much the same to me. Even on Windows you can open the browser console and do > console.log("hello") Just for teaching basic prints, variables, loops and functions, terminal bash on macOS/Linux or Javascript console work just as well as Commodore 64 BASIC. The problem is not that the environment is not available or setup is too difficult. The problem is that there's now way mo…

Teaching bash scripting as an introduction to programming? Surely there are laws against that kind of cruelty?

It's certainly not any worse than BASIC on 1980s home micro's. (IMO it's not any worse than Python either.)

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

#339

Earlier quoted context omitted.

Good grief. What's wrong with going to www.python.org/downloads/ and clicking the big button at the top that says "Download the latest version for Mac OS X"? If you can't even download an installer and run it, then yeah, maybe not quite ready for programming either. Please forgive my snark, but this would be exactly my thought process as a reasonably competent computer user who wanted to learn Python.

He’s right though. When I was six years old, learning to program involved turning on the computer and typing 10 print “hello” run That’s what I want for my kids. And there’s nothing even remotely like it in today’s world.

And then I remember that there wasn't much more to offer, because most "fun" functionality involved POKE'ing 'random' memory addresses.

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

#340
post #314

Earlier quoted context omitted.

If you have a command that doesn't print a new line, the prompt normally ends up on the same line as the output of the last command. iTerm can "fix" this.

See this is where I would rather have my terminal obey the program rather than imposing its own behavior. IMO a good terminal should be extremely minimal, and anything extra should be opt-in.

This is an option that you can enable. It's not on by default.
Post reply on HN