I agree. There are things about Go that are outstanding, like the ease of cross compilation and self contained static binaries making the development of CLI to

I agree. There are things about Go that are outstanding, like the ease of cross compilation and self contained static binaries making the development of CLI tools trivial. However the language design itself is too rigid and inconsistent to allow for software engineering paradigms that even the community itself advocates for. Without highly skilled software engineers at the start, my experience has been that Go projects tend to devolve into spaghetti reasonably quickly. I feel there are a lot of similarities with the JavaScript ecosystem where we see a lot of bad advice in community posts that people feel passionate about. I think Go was an innovative language back in the early 2010s when they started thinking of design patterns to improve the ergonomics of concurrency. Since then I have felt continually frustrated by how close it is to my perfect language but how they just keep missing the mark. I still use it to write CLI tools though. I would use Rust more but it's annoying to cross compile (particularly for MacOS)