Am I the only person that thinks RVM is a symptom of a serious problem? It should not be this hard to manage a software environment.
And by "hard" I don't mean "hard for end-users", although it's quite a lot of hoops to jump through for someone who just wants to get up to speed with the current state of the art. I mean the amount of work that has gone into things like RVM and Bundler and other tools to make developing serious software in Ruby possible.
It's clearly possible to develop serious software without tools like rvm and bundler, the whole world has been doing it for quite awhile before they came about. We did things like putting library dependencies into source control and beating our heads against versioning problems. So I would view them only as steps to a better programming environment.
In fact, I'm not sure a much better approach exists for an environment like ruby. .NET issues patches all the time that magically show up and hopefully don't break things. You don't get side-by-side patch releases. The JVM does have patch releases, and it comes with environment problems similar to ruby. They're often transferred to dev tool users in the form of the JAVA_HOME environment variable.
It seems like the core issues that separate ruby from java come from the existence of rubygems and the fact that it likes to install things globally. So in this way, bundler could be a better solution to the problem that rvm/rbenv solve.
Comments
Am I the only person that thinks RVM is a symptom of a serious problem? It should not be this hard to manage a software environment.
And by "hard" I don't mean "hard for end-users", although it's quite a lot of hoops to jump through for someone who just wants to get up to speed with the current state of the art. I mean the amount of work that has gone into things like RVM and Bundler and other tools to make developing serious software in Ruby possible.
It's clearly possible to develop serious software without tools like rvm and bundler, the whole world has been doing it for quite awhile before they came about. We did things like putting library dependencies into source control and beating our heads against versioning problems. So I would view them only as steps to a better programming environment.
In fact, I'm not sure a much better approach exists for an environment like ruby. .NET issues patches all the time that magically show up and hopefully don't break things. You don't get side-by-side patch releases. The JVM does have patch releases, and it comes with environment problems similar to ruby. They're often transferred to dev tool users in the form of the JAVA_HOME environment variable.
It seems like the core issues that separate ruby from java come from the existence of rubygems and the fact that it likes to install things globally. So in this way, bundler could be a better solution to the problem that rvm/rbenv solve.