experience with macOS has led me to never want software I target to ever be pre-installed. Keeps people from staying up-to-date
-
-
-
I want it to be preinstalled simply so that people don't use "it's not there by default" as an excuse to use Py instead of Ruby
-
happy that homebrew is written in Ruby; cause: ships by default on OSX:
-
I hate having to support deprecated ruby versions simply because they ship by default, though
-
for which software?
-
bundler, rubygems, and cocoapods
-
cocoapods yeah, but surely bundler can require a newer Ruby?
-
we don't want to leave people on system ruby behind, many casual ruby users still use it
End of conversation
New conversation -
-
-
rewrite all tools from perl and python.
-
they shipped python3, so it must not just have to do with deployed scripts...
-
they are already rewritting scripts to python3.
-
but the fact that they shipped py3 must mean that preexisting scripts isn't the criteria.
-
they didn't start shipping it by default until the base system python scripts were able to work with python3 only.
-
but /usr/bin/env python is still (and forever shall be) py2. So they were motivated to ship py3 first.
-
it is easier to rewrite from python2 to python3 than to ruby. btw, are rubyqt and rubygtk stable?
-
I'm not saying every tool should be rewritten in Ruby, but rather that it should be an option.
- 2 more replies
New conversation -
-
-
useful and stable Qt and GTK bindings, plus a compelling argument for rewriting the existing things into Ruby
-
all of the existing things or some of them? Having chef work out of the box on ubuntu is a good reason for me.
-
definitely not all, but having a good story for "this is better in Ruby" is a compelling argument; "it's better for Chef" seems weak
-
there's a reason chef is written in Ruby.
-
(imo) that's not a great argument because it works for anything - Ansible is written in Python, Terraform is written in Go, etc.
-
the question is why ship py2 and py3
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.