Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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 the runtimes for those, and makes sure they remaining binary compatible. Take a program that linked to (and used) the javascriptcore api to add js support. Something compiled 10 years ago will run without recompilation. Thats the bar for stability.


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


They already do.

The installer is the only thing that uses the system one. Could be ported to ZSH or Python 3.


I'd think a script that you pipe into a shell with admin privileges is more likely ;)


Same difference, really.


No: you can sign and notarize packages.


At least for Python the standard .pkg's available from python.org have always been very useful for me. Especially since you can install as many versions as you want simultaneously since they install in separate folders. As a tester who used to have to keep installs of lots of versions this was very helpful.

I should know the situation for Ruby as well... but don't remember anymore.


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.


I try to keep the version of Python my personal computer is using up-to-date; I don't think this is a particularly uncommon thing?


It really is. Like backups. Or unit tests.

Good pratices != common practices.


Over time I’ve just migrated to using brew for everything. I’m not sure how it differs to macports, etc it’s just the one I always ended up using and it’s now just muscle memory :)


It differs quite a bit in its core philosophy with regards to how it interacts with the rest of the system and how much customizability it allows.


The system Ruby is being deprecated, but not removed in this release. By the time it’s removed, Homebrew will likely have a replacement installation process in place.


Macports works and has updated versions of ruby.


On Linux, the Homebrew installer is a shell script that invokes curl https://docs.brew.sh/Homebrew-on-Linux. I guess, they can rewrite the current installer that uses Ruby with a shell version for macOS too.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: