Honestly, I disagree, but I obviously haven’t seen the code in question.

Go has a lot of really nice things going for it:

• very simple syntax - you’re not going to miss a bug because of something small
• obvious error handling - no hidden exceptions to disrupt logic flow - Rust does this well too
• lots of idioms, so deviations are obvious - e.g. channels for synchronization

My problem isn’t with normal program flow, but that the syntax is deceptively simple. That complexity lives somewhere, and it’s usually in the quirks of the runtime. So it’s like any other abstraction, if you use it “correctly” (i.e. the way the maintainers intended), you’ll probably be fine, but if you deviate, be ready for surprises. And any sufficiently large project will deviate and run into those surprises.