2 ms·
>Go has faults. The "OMG Go has no generics so it's total trash" argument is just silly. Generics are coming. Until it has them it's a valid complaint. And the
by HideousKojima 7y ago
>Go has faults. The "OMG Go has no generics so it's total trash" argument is just silly. Generics are coming.
Until it has them it's a valid complaint. And the fact that they're finally coming 11 years after the language's creation is another matter
- throwaway894345 7y agoThis is silly. Lots of people are very productive in Go without generics. Even more productive than many languages that have generics (including Rust). Lots of people are very productive in languages without static typing at all. Generics will significantly improve a relatively small proportion of use cases.
- jimsmart 7y agoFWIW: Java was originally released in 1996, it had no generics, and didn't gain them until 2004 - 8 years after the language's creation. Was Java "total trash" before 2004? Not really, it was still useful in lots of use cases - it just didn't have any generics. Go at least has generics for its built-in collection types (maps, slices) - which, in that respect, arguably places it ahead of where Java was for a whole 8 years. https://en.wikipedia.org/wiki/Generics_in_Java https://en.wikipedia.org/wiki/Generics_in_Java