An alternative opinion: http://www.quora.com/Go-programming-language/Do-you-feel-that-golang-is-ugly?share=1 http://www.quora.com/Go-programming-language/Do-you

An alternative opinion: http://www.quora.com/Go-programming-language/Do-you-feel-that-golang-is-ugly?share=1 http://www.quora.com/Go-programming-language/Do-you-feel-tha... Go's lack of generics kills it for me, as I've learned trying to implement a persistent collection type recently. Without any concept of parameterised types (Foo<A>), programmer defined container types are second class citizens. Casting things to (interface{}) and back everywhere gets old quickly, and you get no static type safety. So in that domain it's essentially back to the C way of doing things, with (void*) everywhere.