> And things like the lack of abstractions and generics are what create a community > that's less reliant on dependencies. "A little copying is better than a l

> And things like the lack of abstractions and generics are what create a community > that's less reliant on dependencies. "A little copying is better than a little > dependency" and you can see it in stark contrast to something like the JS community > with its require('left-pad') NPM ecosystem. The dependency-hell of node projects is in no way whatsoever related to sensible, accepted programming paradigms like generics. Their absence from Go is a widely accepted shortcoming of the language. It doesn't make Go a bad language, and it doesn't reflect on you or anyone in the Go community who enjoy using the language, but you don't have to try so hard to rationalise their absence, especially since they're one of the more prominent things in the Go 2 drafts.