Go and rust are both wonderful languages, but from a startup perspective the conclusion one will always reach is that go is more befitting of the vast majority

Go and rust are both wonderful languages, but from a startup perspective the conclusion one will always reach is that go is more befitting of the vast majority of use cases than rust is. I feel like this business perspective is a little neglected, even though speed of iteration is the main consideration for most startups that are finding pmf. Go is simply more productive to write. Now, for things where performance or memory really matters, rust is beautiful and wonderful (and the language is very fun!). These use cases, like blockchain or specific algorithmic stuff, make rust a compelling choice - the new C++. But for rolling up your sleeves and getting stuff done quickly (aka shipping fast), go is an absolutely fantastic choice. Go seems to be as much as 50% faster to ship features based upon my unscientific observations. For what it’s worth, the only two languages our company uses for backend services are go and rust, so I love both languages (otherwise we’d be using other languages). I find rust to be particularly fun and interesting to code in, but for most microservices, go reigns supreme. It’s simple, readable, and nice generally (though error handling could use some work). For companies with a mature feature set, I’d imagine rust is highly preferable.