The author touches on a lot of reasons I think go continues to be used. For me, its the simplicity really. This ultimate simplicity, and encouraging programme

The author touches on a lot of reasons I think go continues to be used. For me, its the simplicity really. This ultimate simplicity, and encouraging programmers to write simple code (sometimes, I know, at the cost of having more tedious code) is not all bad. The "dogma", and the "it's too complicated" parts of go, while sometimes are indeed a frustration. However, I feel like it has kept the language and the culture surrounding the language largely simple. So both a pro and a con in my opinion. Having worked with go for several years, on many small project and a few large ones. The pros outweigh the cons. One of the bigger ones for me is simply understanding other people's code rapidly. Go projects seem extraordinarily easy to understand without spending hours reading code. When I am in a position to support/operate/scale/troubleshoot other people's code, which is part of my role, this has been a less challenging experience than other languages.