|
|
|
|
|
by tombh
3054 days ago
|
|
It seems odd to me that Golang treats Github as a first class citizen for package management, yet a second class citizen for core contributions. I'm really only a dabbler in Golang, so would appreciate any context. For instance I was affected by the recent go-bindata owner change[1]. The Github user deleted their account and some random user reregistered the original user's name and recreated the repo (albeit seemingly innocently to help everyone get their CIs running again). Actually while we're on the subject, Golang's whole package management experience is surprisingly disappointing :/ [1]https://www.reddit.com/r/golang/comments/7vv9zz/popular_lib_... |
|
OG gophers vendor their deps into their repo and avoid creating dependencies on 3rd party code whenever possible. The Go stdlib is very full featured so it is not unrealistic.
The problem with the go-bindata could be avoided by always vendoring/forking your deps and never trust any VCS provider (e.g. GitHub, Bitbucket, source forge) to handle your critical dependency needs.