Earlier quoted context omitted.
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
macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
161–170 of 450 posts
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#162Earlier quoted context omitted.
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.
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#163Earlier quoted context omitted.
Learning how to install Python and Pip should be part of the learning process for newbies.
Learning how to install and configure development environments is an important skill in general, but I'm not convinced having those skills as a prerequisite for exploring programming as a newbie is at all valuable.
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#164Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#165Ok, this means homebrew needs to be compiled to a native binary!
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#166So what about shell scripts?
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#167How deep you are willing to go with conspiracy theories ... If one was planning to kill off all non-approved software on an OS, what would you do first? Remove all the runtimes that can execute unapproved software of course. Then you are free to impose signing as a requirement for applications and a mandatory app store, and reap the 30% rent tax forever more. Is Apple doing that? Of course, we can't tell. There are l…
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#168Earlier quoted context omitted.
Not true. It's better for them to install it themselves so they know exactly what they're using, and so they type python for python 3 and not python3.
no. it's better for newbies to learn programming rather than fight with operating systems trying to set up an environment to learn programming in
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#169It's interesting to me that this is happening in the same month that Microsoft made installing modern Python as easy as typing Python and then clicking "install". One more piece of evidence that Microsoft cares about developers more than Apple does.
Re: macOS deprecating scripting language runtimes, including Python, Ruby, and Perl
#170Earlier quoted context omitted.
The down side to that is that ruby is currently required to install Homebrew.
You already need Xcode to get Homebrew working, and that will most likely be the vector by which optional scripting languages will be installed.