I was surprised to see such a throwback to the classic PHP article. I can see a value in this article because it brings attention to a lot of gotchas and inconsistencies in the language that we should be aware of; I especially appreciate a good summary of inconsistencies around zero values. However there's a different point to be made here: Golang feels like a successful language to me. It has a purpose and fits this purpose really well. There's a lot of amazing pieces of software that I use regularly that Golang made possible. Maybe this means we should appreciate Go not as a "overall well designed language" but as a language that successfully solved a problem back when a compiled language with great tooling, concurrency and modules wasn't so readily accessible? This reminds me of how PHP successfully solved another important problem, despite its language design problems.
