Go Generics Debate
This cluster focuses on discussions about generics in the Go programming language, including complaints about their initial absence, defenses of Go's simplicity without them, the eventual addition in Go 1.18, and opinions on their necessity and implementation.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Your opinion seems a bit outdated. Go has had generics for almost 2 years now.
Considering what was done with Go before generics it's hard to disagree.
Consider using the D language instead if generics is a problem. Go is what it is and shouldn't change. It has it's advantages that make it optimal for particular contexts. Otherwise you'll turn it into another c++. There is a strong benefit in keeping Go simple as it is.
I think Go is one of the most misunderstood languages. Many people want Go to be something that it isn't, and often for the wrong reasons.Generics are the most contentious issue, and people have been disparaging Go since day 1 for not supporting them. And yet, somehow we've spent the last 10 years writing all kinds of programs in Go, and the lack of generics has rarely been a showstopper. Go does have generics of course -- it just doesn't have user-defined generics. My h
The number one complaint about go seems to be lack of generics. What is academically exciting about generics?
Go will never have generics. mark my words.
If you think Go will ever get generics you are fooling yourself.
If you need generics, Go is not the language you need.
Not another dismissive comment about the lack of generics in Go again.
The Go people don't have an aversion for generics, just a very conservative approach to adding language features. To quote their FAQ:"Generics may well be added at some point. We don't feel an urgency for them, although we understand some programmers do."[1][1] http://golang-jp.org/doc/faq#generics