4 ms·
> This same criticism applies to go and their $GOPATH. FYI, $GOPATH hasn't been a thing in years. Nowadays, the experience around coming back to old projects s
by Mawr 4y ago
> This same criticism applies to go and their $GOPATH.
FYI, $GOPATH hasn't been a thing in years. Nowadays, the experience around coming back to old projects should be on par with what you've described for Typescript.
- chatmasta 4y agoWell then maybe I should check it out again! I've never actually coded anything in Go, but I've had a few occasions where I had to build a binary from source, and I remember having headaches with it then. There is still some $GOPATH stuff in my ~/.bashrc for some reason. Incidentally, and perhaps ironically given the context of this discussion, the last time I interfaced with Go was - about six months ago - when I tried to globally install a binary and ran into some issues [0] which I assume were caused by the same $GOPATH change you're talking about. [0] https://github.com/golang/go/issues/44840#issuecomment-1289664089 https://github.com/golang/go/issues/44840#issuecomment-12896...
- Mawr 4y agoYes, unfortunately there are/have been issues around the $GOPATH -> modules transition. Check out [1] for a guide on the new(-ish) module system. [1]: https://go.dev/blog/using-go-modules https://go.dev/blog/using-go-modules