I don't know that I know of "vitriol", but one common objection is that they will compromise Go's "one obvious way to express an idea" and "simple is better tha

I don't know that I know of "vitriol", but one common objection is that they will compromise Go's "one obvious way to express an idea" and "simple is better than complex" aspirations. And while I think Go will need to add generics in order to compete as other languages improve their concurrency and tooling stories, I also think these concerns are valid--Go is marvelously easy to learn and to read, and there are no languages with generics that can compete in this regard. The rebuttal is that there are many classes of problems for which this tradeoff is suboptimal (Go's type system shows its warts when you need to do any interesting data transformations at all).