3 ms·
What a joke. Go devs spent a decade telling people they were waiting for the right design for Generics to emerge. Finally after a decade they deliver to us... J
by meddlepal 6y ago
What a joke. Go devs spent a decade telling people they were waiting for the right design for Generics to emerge. Finally after a decade they deliver to us... Java-lite generics which are going to require the community to do a massive library ecosystem retooling for next five to ten years similar to how Java felt going from pre 1.5 to 1.5 and beyond.
This language is such a frustrating mess at times.
- atombender 6y agoI'm not sure what you expected. With the exception of Ian Lance Taylor, the Go team has expressed skepticism (and, in the case of Rob Pike, outright disdain) about generics since day one. To anyone who has followed the Go development process at all, this proposal will not be a surprise. The previous proposal was also extremely conservative. Personally, I don't see any other way. Going full-blown generics in the style of Rust/Haskell/OCaml, for example, would drastically alter the language. This is closer in scope to, say, Modula-3.
- meddlepal 6y agoI'm more frustrated that it took a decade to get to this point. Not that it is not more powerful.
- ccktlmazeltov 6y agoThen why do you use it? I'd rather have no generics in Go, maybe you can try Rust?
- meddlepal 6y agoBecause I have a job that pays good money working in Go. Doesn't mean I have to be happy with it.
- ccktlmazeltov 6y agoInteresting, the reason they chose Go is probably due to its no BS aspect. But forcing to make java/C++ people work with it actually makes the language worse. Interesting.