Go seems to be picking up a lot of python/rubyists who are looking for a faster language that's not excessively verbose. I suspect that fraction of the community doesn't miss generics as a result of simply never having had them.
The need for generics (or macro/template-based equivalents) naturally falls out of using a statically-typed language.
I thought the whole point of picking a language like Ruby was to use a language in which you can describe what you want, instead of how you want it.
Boy oh boy do I ever miss collection-level constructs like map and reduce in Go. I just don't think of them as 'generics' because I'm not very well-versed in statically typed languages.
I still bite the bullet and use Go anyway when it feels appropriate, because I can get fast type-checked programs with a reasonably quick prototyping cycle.
Plus after you get types down well enough, you can largely pretend you are using a dynamic language. For instance sometimes I write my functions, make sure they work right, check the type ghci says they are in the repl, and add the type annotation.