I remember reading a comment from one of the go developers that the lack of generics is not some big design decision, it just didn't make it into 1.
The more defining features are goroutines and the type system. (Structs, embedding, interfaces, ...).
Go has multiple built in generics anyway. (Slices, maps, channels), so it's not like it could be some big principle to not have them.
Generics would take away the ridiculous amounts of boilerplate that go requires, and make the language much, much nicer to use.
And safer too. The amount of `interface{}` in a lot of go code is such a smell.. always makes me wonder what the point of using a statically typed language is if you use interface{} and type casting all the time.
The more defining features are goroutines and the type system. (Structs, embedding, interfaces, ...).
Go has multiple built in generics anyway. (Slices, maps, channels), so it's not like it could be some big principle to not have them.
Generics would take away the ridiculous amounts of boilerplate that go requires, and make the language much, much nicer to use.
And safer too. The amount of `interface{}` in a lot of go code is such a smell.. always makes me wonder what the point of using a statically typed language is if you use interface{} and type casting all the time.