goop

What do GOPATH, the project folder structure, package management, and package versioning all have in common? The go command. Not the linker, not the compiler -- the `make` replacement. If you want to fix the most broken parts of Go -- its ecosystem management tooling -- just replace your `go` command. I have, and I love working on a project with a proper top-level src folder, with vendor-able packages discoverable in a top-level lib folder pinned to known-good commits. There are literally dozens of go replacements, but the winning combination for me is using Goop [1], Makefiles, and symlinks to subvert `go get` and the naive way it parses import declarations [2]. [1] https://github.com/nitrous-io/goop [2] https://golang.org/ref/spec#Import_declarations

I keep meaning to spend some time playing with Go, but I haven't yet so I don't know how that feels. However, I wonder what it says that several dependency management tools have emerged for Go. https://github.com/mattn/gom https://github.com/nitrous-io/goop https://github.com/tools/godep