Re:How to start a Go project in 2018
by rco8786 on Monday May 14, 2018 @09:07AM
(#17065122)
That’s, like, the opposite of npm though. It does dependencies per project, versioning, and does not impose any filesystem restrictions. Not that it doesn’t have issues.
[ Parent
| on HN ]
How is it the opposite of npm?
All of the reasons I listed...?
But npm does all of those...
I know...Golang does the opposite of each of those. Here's some excerpts of the comment we responded to:
> It's distasteful of Go to impose a filesystem layout.
> To achieve [self-contained dependenceis] with Go, one has to set a different GOPATH per project, and then checkout the project deep into that root.
> Given that Go doesn't really do package versioning...