4 ms·
> GOPATH, which is smart because it turns out a huge percentage of devs don’t know what env vars are or how to set them. This gave me a laugh but it’s not fair
by parhamn 6y ago
> GOPATH, which is smart because it turns out a huge percentage of devs don’t know what env vars are or how to set them.
This gave me a laugh but it’s not fair! I’d guess most of the GOPATH outcry was the annoyance around managing automated and other non-dev environments.
- Groxx 6y agoAlso at having to put your source in the gopath at its import path. So you couldn't have 'project/' and 'project2/', you had to have 'gopath1/src/path/to/project/' and 'gopath2/src/path/to/project2' or you had absolutely no isolation between things (until vendor (and that leaks (and it still requires that deep folder structure in some cases (and it took them quite a while to accept it in core tools)))). GOPATH was nothing short of a monstrosity. Its problems were truly obvious on day 1, but it lingered and infected everything.
- earthboundkid 6y agoI don’t agree that it was a monstrosity. I do agree that developers didn’t like having to include “extra” folders. I think even just making a GOSRC var and dropping /src would have bought good will. (Go has a GOBIN.)
- jrs95 6y agoI still use this directory structure and it doesn't really bother me honestly. Makes it very easy to work with multiple local repositories without having to worry about any linking or installing bullshit you have to do with other systems.
- parhamn 6y agoIt is certainly remarkable how long this is effective for in Golang. Libs just don't break.
- xrd 6y agoAre you sure you aren't discussing lisp here? :)