> My honeymoon with the #go language is extremely over.

> This article is going to have a different tone from what I've been posting the past year - it's a proper #rant. And I always feel bad writing those, because, inevitably, it discusses things a lot of people have been working very hard on.

> If you're already heavily invested in Go, you probably shouldn't read this, it'll probably just twist the knife. If you work on Go, you definitely shouldn't read this. I've been suffering Go's idiosyncracies in relative silence for too long, there's a few things I really need to get off my chest.