[mazatta]

Exactly. I'm curious if the author continued using Go for a bit of time, if they would still write the same article.

Some of the concepts the author took issue with, such as receiver arguments or multiple return values never felt all that unusual for me, but that's probably because I'm quite familiar with a language like Python, where these concepts are pretty common if you've ever written a class or written a function that `return a, b`

The final argument, that Go's concurrency is somehow not concurrency, or all that special is a bit too much for me. That section needs some editing, but if anything, they unintentionally make the point that Go's concurrency IS simple.