I find it amusing how angry people get about this, like really, vehemently angry.
If this issue is so important to people, don't use Go, use C++, Java, D or Rust. Don't waste your life arguing about something you'll never use, it's not a productive use of your time! Think about how much time you could save!
Alternatively, propose a solution to the problem and try and gain some traction to get it implemented into the language, or fork Go and implement it yourself. There's evidently a hunger out there for generics in Go, but everyone keeps assuming the responsibility lies with the Go Core team who's priorities seem (right now) to be in the optimising GC/compiler area.
I was thinking this exactly. As an external observer (I don't use go, don't intend to. I do look to it as an interesting example language though) all the vitriol is very puzzling.
And you're right, the Go core team does not seem interested in adding generics anytime soon.
Personally, and this is my opinion, I find myself wondering if old school hackers like Thompson, Pike, and Fitzpatrick (and others) find themselves not needing generics, or that slice/maps are enough, maybe I should ponder that for a while. Ie do they know something I don't? Edit; or maybe the type of software they're creating with go is different than I as a generics user, am creating?
>or maybe the type of software they're creating with go is different than I as a generics user, am creating?
Or maybe their work is mostly creating Go, not using it, so they wouldn't care?