It’s totally reasonable to want to organize projects in a different way, but I think GOPATH’s caveats are overstated. - It’s an evironment variable, which make

It’s totally reasonable to want to organize projects in a different way, but I think GOPATH’s caveats are overstated. - It’s an evironment variable, which makes it relatively easy to modify. To switch your dependencies from one pool to another, you can modify your GOPATH. - The vendor directory lets you pin your dependencies per-project without modifying GOPATH. It’s not the most beautiful solution (and Go doesn’t often offer the most beautiful solution to any particular thing), but it’s workable.