[aeturnum]

Having shipped a little golang code (back in ~2017) and having watched things evolve, my sense is this:

- Golang doesn't fit comfortably into the spectrum of "low level & fast v.s. high level and easy" languages, largely because it does go in different directions in many ways (see: critiques on their garbage collector, type system, etc).

- Smart people are happy with Golang, but the fact that it makes different choices means that people regularly discover to their sorrow that the language isn't quite what they expected.

- In general, most of the "go was wrong for us" stories seem to come from companies that use it as a side language. Teams where Golang is their main workhorse generally seem at peace with its choices.

To me, it means I have no doubt you can build a company on Go - but maybe build that experimental high-performance replacement for a python service in Rust.

[zozbot234]

"Teams where Golang is their workhorse" probably made that choice a long time ago and have a lot of legacy code in the language. Staying with Go for the most part is just the sensible thing to do in that situation.