News for hackers. Stuff that matters.
Re:Deno Is a Browser for Code by parhamn on Thursday May 28, 2020 @10:37PM (#23345747)
> 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.

Re:Deno Is a Browser for Code by Groxx on Thursday May 28, 2020 @10:42PM (#23345768)
Also 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.

Re:Deno Is a Browser for Code by earthboundkid on Friday May 29, 2020 @12:08AM (#23346176)
I 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.)
Re:Deno Is a Browser for Code by jrs95 on Friday May 29, 2020 @01:33AM (#23346565)
I 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.
Re:Deno Is a Browser for Code by parhamn on Friday May 29, 2020 @12:00PM (#23351573)
It is certainly remarkable how long this is effective for in Golang. Libs just don't break.
Re:Deno Is a Browser for Code by xrd on Friday May 29, 2020 @02:04AM (#23346720)
Are you sure you aren't discussing lisp here? :)