Some time ago I blogged about how we stopped using RVM in production: http://blog.arkency.com/2012/11/one-app-one-user-one-ruby/ http://blog.arkency.com/2012/11

Some time ago I blogged about how we stopped using RVM in production: http://blog.arkency.com/2012/11/one-app-one-user-one-ruby/ http://blog.arkency.com/2012/11/one-app-one-user-one-ruby/ . Many people here said that RVM might be over-complicated for the simplest cases and I think in production when there is only one app is the most simple usecase that you can get and RVM is overkill in such situation. In development however RVM is awesome, especially when you are a contractor or freelancer or you work on multiple open source ruby projects and gems and must switch between ruby versions often. Michał Papis, the current maintainer is a great person and I wish him best luck in funding the project. If you want to meet him in person, he will probably be at wroc_love.rb 2014 conference ( https://twitter.com/wrocloverb https://twitter.com/wrocloverb ) . Check out what he learned so far on working with RVM1 and what are the plans for RVM2: http://www.youtube.com/watch?v=wN-iIC3S1ZM http://www.youtube.com/watch?v=wN-iIC3S1ZM . I remember that some of the ideas for RVM2 were invented after our Ruby User Group meeting at 3 a.m. in the night, when we were trying to think about most science fiction approaches to RVM such as even a client server architecture. That was a crazy night :) The biggest problem with RVM1 is that it is written in shell and even if there are people from Ruby community that would like to support this project, their skills are in Ruby language, not bash or zsh, etc. There are plenty of people who would like to help maintaining RVM but they just hit the wall when they see the amount of bash code in the project.