I actually hope this doesn't take off (or at least, if it does, that it keeps its scope in check). RVM is invasive and moderately broken because of that.<p>And besides, in a very short time, Go is going to commit to API stability with Go 1. And given that, and static typing (even at runtime), and Go's beautiful module system, and the fact that static linking is the norm, all means that worrying about which Go version you are running on is a silly concern.<p>This tool purports to solve dependency hell, but dependency hell, especially in a language with no stable ABI where everything is compiled from source, is entirely about package management. Go's standard library used to be in flux, which made pinning a version an important piece of ensuring source compatibility with packages. That's about to go away, and I hope GVM-like tools will follow.
Because Go builds statically linked executable files, the GVM tool only applies to development environments.<p>As far as the development environment is concerned, I find it easy to manage multiple versions of Go by setting $PATH and $GOPATH as needed. I only work with a couple of versions of Go at a time and I don't share packages between versions of Go, so my situation might be simpler than what they have at moovweb.<p>I expect that I will mostly use a single version of Go after Go 1 is released next week.
I kind of think of RVM as a necessary bug due to the unmanaged span of Ruby versions.<p>I am not clear why this is really necessary for GO. Why not just use 'go fix'?
This is slick. I will note though, if you're just getting started with Go or if you only have small projects, this is overkill. `go fix` and just starting out with current weeklies (RCs for Go1) is sufficient. For projects of any substantial size though, this looks like a nice handy tool!