2 ms·
I don't agree that Go's tooling is what makes it popular. Mainly because it's tooling is not very good. All of the vendoring tooling is broken in one way or ano
by cyphar 10y ago
I don't agree that Go's tooling is what makes it popular. Mainly because it's tooling is not very good. All of the vendoring tooling is broken in one way or another, the linters and vet-checkers have questionable advice in some cases, and not to mention that the standard library has so many quirks that come from the fact that Go is trying to be system programming language that hides details about the system from you.
[ Disclaimer: I'm a maintainer of runC and have been programming in Go for many years. But that doesn't mean I have to like the language. Give me C any day. ]
- XorNot 10y agoComparing vendoring tooling for Go and C in C's favor seems odd. Personally I think Go actually makes a pretty bold statement about dependency management: people don't know what they want. I also have a sneaking suspicion Git and Github's interface in no small part to blame. Golang for me made me come to one important realization: if I can't build a project by just cloning the git repository, then why the hell not?
- majewsky 10y agoOr related: If I cannot build a project by just cloning the repo at any arbitrary location, then why the hell not? If you have not experienced this before, try cloning a repo that uses Go-1.6-style vendoring anywhere outside the GOPATH.