News for hackers. Stuff that matters.

A comment on Go's old $GOPATH story for development and dependencies. Parent comment

Re:Go's old $GOPATH story for development and dependencies by quectophoton on Friday May 24, 2024 @04:07AM (#40464045)
> but in practice their theory didn't work out (for various reasons)

For me, one of the reasons I disliked $GOPATH is that source code was not in $GOPATH; it was in `$GOPATH/src`.

The fact that they are very strongly against relative imports also didn't help, even if I get why they do it.

[ Parent | on HN ]
Re:Go's old $GOPATH story for development and dependencies by demi56 on Friday May 24, 2024 @04:41AM (#40464214)
From my experience the reason $GOPATH has pkg, bin src directory was they wanted to limit spread of affecting the filesystem, I could zip my go directory put it in another computer and still works as good as before, I hated Python because it couldn’t do this even pyenv have high chances of it not working correctly if changed to a different distro and most times I don’t wanna download 500M of anaconda everytime I swap.
[ Parent | on HN ]