Meh, I’ve programmed in both. Rust is “hard”. I wouldn’t ask a company to write in it, because it might be hard to get devs for it. However, open source is different. Rust is not hard enough for most developers to learn, and most developers love it when they learn it. On top of that, GoLang is practically an expert in hidden, annoying bugs that rust almost categorically eliminates. Golangs panics don’t backtrace unless you write them in a certain way, you have to know the golang “culture” of error handling, and then without a good match statement or ? macro you are left with ifs under every goddam line of code to do your own manual error checking. Golang goroutines are not as intuitive as one might think with how they close when the scope they come in from closes and their channel patterns. And the “context” passing takes a long time to learn how to do right. It’s an intuitive language at its core, its docpage being one page, but it’s culture is like python’s, needing a year or more to really know what best practices are. I tbh think they are just about exactly as hard as one another, but one, golang, leads to more bugs. Compile time is not that important when you can ensure that at compile time the thing will run.

Refactoring rust sucks, but by keeping your structs small you can usually avoid it.