I think you described it well. The go designers spent a lot of time on the end to end full workflow, and not just on the language. And had production constraints in mind for working on a backend service in a team at a boring tech company.

That's also why I think Go will forever be a "to each his own" language. By targeting that lowest common denominator, choices are made for you, some people will always dislike it, and others will always love it.