Go: Best Practices for Production Enviroments
I really like Go, and have been getting into it quite a bit. It's powerful, quick, and fits in nicely as a "native code" utility language, which I dig. However, the first thing the OP talks about, $GOPATH, really fricken annoys me. I know that's sort of silly, but hey.<p>Are there any good fixes for this at all? What other ways of tackling the dev env are there for Go?