The reason Go is popular among certain large organizations is because it solves the problems that large organizations face with a minimum of fuss. It gives you a uniform coding standard that's enforced by a tool. It shortens compile times to almost nothing. Its performance is "acceptable" - not as fast as C++, but not so much that you'll blow lots of $$$ on AWS bills. It's got a rich standard library, and common interfaces that most third-party libraries actually use. It encourages developers to be explicit about their intent, to write out all of their algorithms in full detail, and to handle all error cases in depth.
It is not a language where an individual developer without the constraints of a team will be maximally productive. It wasn't designed for that.
I've found that personally, I enjoy programming in Python, Rust, or even Javascript or C++ more. But I can at least respect the language designers for making the choices that they did, given the constraints that they operate under. The article seems determined not to do that.
I would have thought that, if you don't like something, just don't use it. I personally am not an enormous fan of Peanut Butter. I don't go off on rants as to why Nutella is far superior, or why peanut butter is just peanuts for the toothless etc. I just don't buy peanut butter.
What is so hateful about Go that seems to offend people to the point where they expend large amounts of energy ranting about it?
Yes they've made some choices that are controversial, but that's true of every language.
Good luck in the wonderful world of the Internet! People love that shit here.