Hacker News new | ask | show | jobs
by gverri 4726 days ago
My tip: DON'T USE RVM. (rbenv is a good alternative)

RVM is the nÂș1 source of problem in Ruby envs.

3 comments

RVM is not that terrible. If your biggest difficulty in Ruby or Rails is RVM, you haven't been around long.

The cause of problems for beginners is quite simply "change". Rails has been through a few major revisions now, and the jump from 2 to 3 dropped a lot of people (even though 3.1.x+ has been fine), and I doubt many will drop again from 3 to 4, even though there are some big changes. The problem is that with all of the changes comes a bunch of now inaccurate information that no one will update that is found easily, some with high point rankings in S.O.

The more important problem to fix though is leadership. DHH has done a great job, but either he or someone else needs to be more vocal as a single voice leading Rails. It is led by committee currently, and it shows in the lack of vision. However, despite its problems, I'm in it for the long haul. I like it a lot better than everything else.

I'll admit having a custom "cd" makes me really itchy, but rvm is the path of least resistance (mysql and ubuntu are the same: itchy PLR)

http://railsinstaller.org/

Seeing that rbenv's install procedure is slightly longer than RVM, I wouldn't suggest it for beginners.