RVM can really bite you if you are not careful. And it can really mess things up <a href="https://github.com/wayneeseguin/rvm/issues/1234" rel="nofollow">https://github.com/wayneeseguin/rvm/issues/1234</a><p>Right now I am looking for an alternative on my servers, because I need different Ruby versions across projects.<p>It is very interesting history following the development of RVM, to Rbenv and now also Chruby. It seems like 37signals is going the way of Rbenv.<p>It will be interesting to follow. It seems like a really fundamental problem, that need to be solved for us to build good software.
This post is 30% technical, 70% politics.<p>Essentially, the author is upset that the author of rbenv[0] decided to criticize rvm instead of opening tickets and whatnot.<p>The author then goes on to blame the rbenv author for the year long delay in implementing PROMPT_COMMAND in rvm.<p>> We could have this code available for rvm users one year ago, possibly we could have a lot more of good solutions if the problems were discussed instead of throwing accusations as it was done by rbenv author.<p>[0]: <a href="https://github.com/sstephenson/rbenv" rel="nofollow">https://github.com/sstephenson/rbenv</a>