Rust vs. Go in 2023
&gt; You may have read articles and blog posts aiming to convince you that Go is better than Rust, or vice versa. But that really makes no sense; every programming language represents a set of trade-offs. Each language is optimised for different things, so your choice of language should be determined by what suits you and the problems you want to solve with it.<p>That&#x27;s sort of true, but I wish people would stop cowardly saying that you <i>can&#x27;t</i> say that one language is better than another <i>overall</i>. That&#x27;s clearly not true.<p>IMO this article is very very long and doesn&#x27;t really highlight the differences well, which IMO are:<p>* Go has much faster compile times.<p>* Rust&#x27;s tooling is very good but I would still say Go&#x27;s is better. It has built in fuzzing support! Cross compilation is as simple as setting an environment variable.<p>* Rust is a <i>little</i> faster, and avoids GC.<p>* Go&#x27;s standard library is much more comprehensive than Rust&#x27;s.<p>* Go is much easier to learn and to read.<p>* Rust is a better language if you <i>have</i> learnt it. It has much more powerful features (especially the functional ones) and is more principled. Going back to Go from Rust is frustrating.<p>* Rust has a much stronger type system and the borrow checker. Both make bugs far less likely.<p>* Async Rust is probably the worst bit about Rust. Go&#x27;s goroutines are much easier to use. Though I would say traditional multithreaded code in Rust is pretty easy - it&#x27;s just that a lot of the ecosystem forces you into async.