Personally, I don't understand the hype of rubyenv. I really love rvm. I'm not sure why the author called rvm a "mess of bash scripts". I guess because rvm has a lot of features? If I did not care for gemsets and all of the other niceties that rvm has, I guess I would be on the market for another ruby manager. The fact that the author of this article was rubbed the wrong way by Wayne and rvm, rubbed me the wrong way.
He probably called it a "mess of bash scripts" because, uh, it is a mess of bash scripts. Have you looked at the implementation? RVM is amazing in the functionality it has, don't get me wrong, but it hacks into your shell in some nasty ways and when things go wrong good luck figuring out why without diving deep into the underlying bash.
When you have a new box, or when things go wrong, is probably the time to try out "rvm implode" and try rbenv. Reinstalling rubies takes some time and it looks like there might be some time required to configure/fix existing apps to use rbenv?
Part of the problem is that it overrides extremely low-level things like cd. That can get in your way pretty badly if there's a bug, or just a feature you don't understand.
this is not quite correct. it has a configuration option for this and you can set it to false. it was actually set to false as default for a while after rubyenv was released but then it reverted to true by default as I suppose it a better option for most users.
but again, if you don't like this part of rvm, just switch it off
