A huge variety of other languages have successfully implemented generics. The Go team seems to be looking for some mythical ideal solution with no tradeoffs, and will therefore never do it.
Re:Why Go Is Not Good (2014)
by omginternets on Wednesday December 09, 2015 @11:47AM
(#10704804)
>A huge variety of other languages have successfully implemented generics
Completely irrelevant; the argument isn't "generics are hard [full stop]". The argument is "generics are hard" AND "we don't know Go's niche well enough to commit to any specific approach".
Re:Why Go Is Not Good (2014)
by mike_hearn on Wednesday December 09, 2015 @12:27PM
(#10705113)
But how can they not know that, after so many years?
Re:Why Go Is Not Good (2014)
by omginternets on Wednesday December 09, 2015 @02:40PM
(#10706162)
You'd have to ask them, but I suppose it takes years to carve out a niche.
What I can say is that I recently interviewed a Google engineer who was conducting a survey of Go's usage, so it seems they're at least studying the question.
The response I've overwhelmingly observed from qualified voices isn't "boo generics!" but "generics are terribly difficult to get right, and we want to know more about Go's niche before making any design decisions in that realm".
I suspect you're reading a lot of drivel from web programmers who discovered net/http last Thursday. It's hard not to be frustrated with the internet, I concede...