(Toby Nieboer) #1

Everyone seems to have a favourite Ruby version manager but I haven’t seen much discussion of the pros and cons of each one.

So which one do you use, and why?

(Nick) #2

I’m on RVM.

Biggest reason why is familiarity, and it works well for me for what I’m using it for all these years.
Due to the familiarity, I haven’t really found myself looking at the other options.

(Lee) #3

ASDF as it allows you to manage more than just Ruby. If you using multiple languages like Python, Erlang and Ruby or more - then you can manage these with this instead of using individual language managers.

Previously I used RVM which is a standard install and referred commonly in tutorials online. It’s maintained well and the handling of gemsets makes for cleaning out your computer much more manageable.

(James Darryl) #4


(Htmldrum) #5

more features for deployment and config mgmt integration - runs PGP checks on rvm binary, less issues with rvm_path set up for workers vs web processes vs system ruby.

for dev, rbenv is fine. the two share a syntax about active ruby version which ops can bridge