Why Golang Is Bad for Smart Programmers?

This is a few years old now, it's age made clearer by the lack of generics.

I don't really agree. The more experienced Devs I know enjoy Go's simplicity. Personally I miss pattern matching and algebraic types, but I am fully able to live without it them and the proposal around using interfaces looks interesting.

He got it backwards: "smart programmers" are bad for programming.

How smart can you really be if Golang is what's holding you back? It's a fine language, but definitely NOT a language that encourages clever abstractions and riddles - but that has nothing to do with being a smart programmer. Some would argue that smart programmers are drawn to simplicity (and accomplishing things IRL) and it's the fools who chase pie-in-the sky abstractions.

Go is the prefect enterprise language for much of the reason pointed out in this article. I think Google created it to essential turn programmers into high performance robots. You are very limited in what you can write. It's simple to read and learn. It's easy to deploy and maintain. It's pretty much fast by default. All the tooling is built into the language. It probably a great language to have a job in as well for these reason, but there is almost no room for fun and creativity in Go.

If you want to have fun and get creative programming no way you are picking Go. It has to be the most boring language I have ever used. I think that only cool thing I did in Go that made be say "Wow this is cool" was building code generation tools.

Google created it for novice programmers, mostly fresh out of college, that they wanted to be able to fire easily. This is a stated reason from the early discussion about design rationale, and is alluded to in the OP. There's also a number of features (especially in older versions) that seem to only make sense when using it in a monorepo like Google does (which also stores built binaries in version control), such as the way imports work and the way `go generate` works.

It blows my mind when people ignore these and make post hoc justifications about why its design is "good, actually" for projects outside of Google. They released the language to the public in order to condition the labor force and make onboarding easier.

Boring is good; languages are a tool for communication. If you want poetry, there are lots of side projects to create new dialects atop existing languages (including Go).