> The generic dilemma is this: do you want slow programmers, slow compilers and bloated binaries, or slow execution times?
I don't think these are the only outcomes, but lets go with it. A slightly slower compiler then. Solved.
> The generic structures are less useful than a concrete one.
If they weren't more useful then nobody would be arguing for them.
> Generic structures can be less optimized than a concrete solution
Ridiculous.
>Code won’t look idiomatic.
Idiomatic is a function of the language syntax and features. If generics are a feature then their use will, by definition, be idiomatic.
And on and on. At this point people using Go accept the lack of generics (and, oddly, sometimes wear the omission as a badge of honor). I don't think anyone happily using Go is expecting generics anytime soon, if at all. And I don't think the authors need a paper to show their dislike for them. Who are they trying to convince anyway?
EDIT: A few folks have told me I come across too heavy handed in my reply. I apologize to and don't mean to discourage the author(s)! It's a tough document to write. Especially if this was just a starting "brain dump." The document title had just set my expectation towards a neutral tone.