I think the way it's meant to be read and understood is as follows:

"There may (or may not) be many problems with Go, but building bigger projects is not one of those".

This is actually kind of funny because one of the classical arguments made by gophers eight or so years ago when I first started learning it was that golang's limited abstraction power makes the pain of large codebases obvious enough that teams are incentivized to keep projects small.

A form of whataboutism.

Well... It kinda replaced Java for most cloud stuff except for Kafka.

Or the related fallacy, "X was designed to be good at Y, so clearly X is good at Y!" (or worse, "is the best way to do Y!").

I basically mean:

No matter if you dislike Go you cant argue with the fact that it is a good fit for larger teams collaborating on a big multi-year/multi-decade project.