Not person you're replying to but I'll bite. I think Go has some pretty good thoughts behind it's design. That is not to say that it is perfect by a long shot.

Not person you're replying to but I'll bite. I think Go has some pretty good thoughts behind it's design. That is not to say that it is perfect by a long shot. Lack of generics is the main reason I've not actually tried to write any. But I've looked at some, and even helped debug a tiny bit. And that was the -nice- thing about it; the patterns are simple enough that you can learn it quickly. The drawback is that you have to write a LOT of code (or Interface hackery) to make complex things. And, on one hand, the syntax is still the same. On the other hand it's still more code to write. I think about C# a lot when I think about Go's simplicity; I'd argue there's a sweet-spot in C# where you COULD write code that is expressive and easy to understand but still more flexible. However, at this point there are 3.5 different ways I can think of off the top of my head to go through an Array/List in the language. In Go there's usually not too many ways to do the needful. That's an advantage for newcomers, but the proverbial ceiling isn't glass; it's hard iron, and you can't go above it.