That being said, I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity.
I completely understand that introducing that in the language it's a pandora box, etc etc (not only because of compiler's complexity and compilation speed).
But still, I have to find a way around that, being DRY has obvious advantages (although depending too much on obscure magic can be a problem); it's not just a random language feature from my favorite language.
I'm trying to see whether https://github.com/droundy/gotgo helps
Can you give any concrete code examples including a description what you would have liked differently?
The problem is that Go simply doesn't solve anything new. If Go contains your favorite language features but not mine, then why should I bother to use or hype it?
If you want lightweight concurrency with GC you could have gone with Scala, Erlang, or Haskell.
No, you just got hit with the typical Go activism reply when someone mentions issues with the language.