4 ms·
Thus solving Go's dependency management problem once and for all.
by colonelxc 8y ago
Thus solving Go's dependency management problem once and for all.
- eikenberry 8y agoSolving it by giving it a worse one.
- MoOmer 8y agoThat is the joke.
- littlestymaar 8y agoWorse than pulling master on github, really ? Npm has issues, but it's still way better than the state of the art of dependency management in Go. Left-pad was bad but the problem was fixed on npm's side after a couple hours. Go's equivalent isn't fixable: https://mobile.twitter.com/davecheney/status/855049071307792384 https://mobile.twitter.com/davecheney/status/855049071307792...
- mappu 8y agoPulling master on github isn't the "state of the art" for Go (it's dep and vgo).
- littlestymaar 8y ago`dep` is pulling directly from github … And `vgo`, while promising, is still a protype not ready for production[0]. [0]: https://github.com/golang/go/wiki/vgo#current-state https://github.com/golang/go/wiki/vgo#current-state
- cdoxsey 8y agocommit your vendor folder