I loved Go's simplicity when it came out. However, it has become clear to me that it was a little too simple to handle all the new requirements and additions t

I loved Go's simplicity when it came out. However, it has become clear to me that it was a little too simple to handle all the new requirements and additions that came after v1. That's how you get weird comments-as-code (// +build linux,386 darwin,!cgo), strings-as-attributes (tags), tacked-on modules versioning / vendoring, non-typed generics( interface{} everywhere), somewhat-typed generics (go generate), etc. Go was not quite ready to handle all these directions people wanted the language to stretch to and as a result it's now already full of annoying warts. I'll still pick Go if I need a simple service with amazing performance. Funnily enough though, I have no need for any of the (non-performance) additions that came after 1.6.