Hacker News new | past | comments | ask | show | jobs | submit login

This seems like a description of NPM in the node ecosystem, they are incrementally solving all these issues.



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.


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...




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: