> Second, we know that many people have said that Go needs generics, but we don’t necessarily know exactly what that means. Seems like the go authors are still

> Second, we know that many people have said that Go needs generics, but we don’t necessarily know exactly what that means. Seems like the go authors are still bent on the idea that generics are really not necessarily and that there is no such problem that can only be solved by generics. Then is the generic drafting only a thing because they have been pressured into it by the community? I wonder why Rob Pike one day decided that it’s okay to change a language he almost vowed to never change after the initial release.