Trying Out Generics in Go
Honest question:<p>Do you think Generics will be an overall win for the Go language, or will they be overused / end up making code harder to read / harder reason about?<p>I kind of hate looking at Go code containing generics.  What previously was elegant and easy on the eyes is now annoying and muddled by the additional layer of abstraction.  I'm saying this with sadness, as someone who fell in love with Go back in 2012 and still writes it at least weekly.<p>Is it a better bet to move on and go full Rust, rather than bother with wherever the goggle golang train is headed?<p>p.s. Even though code generation is [also] annoying and perhaps not ideal, I've rarely needed to use it and kind of liked that it was inconvenient - forcing me to think about problems differently.  Certainly some problems will benefit from the addition of generics, but is it really enough to justify the added complexity?  I wonder if this is a case of tragedy due to vocal minority.<p>p.p.s. Generics in other languages like Java or Scala seem fine, as they are "kitchen sink"-style "all things to all people" languages.  Such behemoths are nearly always clunkier and less easy to read than pre-generics Golang.