On: Taking Go modules for a spin

[weberc2]

I like the consistent, sane project structure, but GOPATH is an odd duck to be sure.

[majewsky → weberc2]

I actually started using the GOPATH structure for all my repos after discovering three full checkouts of github.com/torvalds/linux [1] on my drive.

[1] I know it's not the official upstream remote, but I find this one the easiest to remember.

[weberc2 → majewsky]

I do the same, but I don't like that it is searched by default when building a Go program. It's too easy for the versions of dependencies in those directories to have changed. And even if you vendor, it falls back to GOPATH so you can still bring things into your build by accident.