It's pretty well split down the middle from my experience on these topics. And few people are really ravenous for them. However, you're talking about selection

It's pretty well split down the middle from my experience on these topics. And few people are really ravenous for them. However, you're talking about selection bias. If generics were something you absolutely wanted, you probably wouldn't be using go in production. One of the things you learn when using go is that generics are not the answer to everything. They are certainly the answer to some specific things, like optimal implementations of common algorithms.... But not every application needs to use the A* algorithm, or a left leaning red black tree... Would I like to have generic implementations of those that I could just toss in my application with my own types? Sure. But I've done enough generic programming to remember when you could finally stop writing foo<bar<baz, bat> > And could finally do foo<bar<baz, bat>> .... And I don't really want to have to write that kind of code again.