Been there, done that, been happy with the approach.
As for Go, I do like the language- well enough that I took another job where I'll be mostly using it. I can't quite shake the feeling that some of the syntactical and stylistic choices were made more to be different than because they are better, but I can move past them. I think goroutines and channels have a lot of potential as atoms of concurrency for building models going forward, and I think it's nice to see a language gaining popularity that is focused on being small (in the sense of the size of the spec) and simple (in terms of feature interactions). I don't think a lot of it's potential has been realized yet, and I hope that we can take some of the lessons learned from other languages, e.g. Conduits and FRP from Haskell. For right now I've seen enough cases of people introducing threading errors and problems introduced by the user of pointers that I think it pays to be wary of third party libraries.