I haven't heard anyone, including the go authors, say that generics are bad and you absolutely don't need them in Go. Personally I like Go a lot and don't miss

I haven't heard anyone, including the go authors, say that generics are bad and you absolutely don't need them in Go. Personally I like Go a lot and don't miss generics much, but for some things I'd love to use generics some day. It's basically about trade-offs eventually. To quote the FAQ about it: > enerics may well be added at some point. We don't feel an urgency for them, although we understand some programmers do. > Generics are convenient but they come at a cost in complexity in the type system and run-time. We haven't yet found a design that gives value proportionate to the complexity, although we continue to think about it.