I have used Rust professionally for two production projects that see daily usage in our company. One is a rewrite of a small C# HTTP application service. The second is a from-scratch automation library with CLI and HTTP service end-user applications. I chose Rust for its safety, runtime speed, and useful abstractions.
On several occasions I've received strange messages or suggested reading from coworkers that usually goes something like "here, look at this: this is why Go is better than Rust. You should have used Go."
Here's what I think.

"Rust or Go?"

I don't believe there is a single right tool to do any job. I do believe there are better tools for doing some jobs, and tools that are decent for most jobs. I also believe that Go and Rust are two very different tools for doing very different jobs. Why do these programming languages get compared a lot? Is it because they're both AOTC, statically-typed, "server-side" langauges?

From golang.org:

Go is an open source programming language that makes it easy to build simple, reliable, and efficient software.

And from rust-lang.org:

A language empowering everyone to build reliable and efficient software.

Wow, yeah looks like they are both trying to solve the same problem. Both claim to allow programmers to build reliable and efficient software. So maybe the difference isn't what they're trying to solve, maybe it's howthey're each trying to solve it.

Let's look a little deeper. From the Go documentation:

The Go programming language is an open source project to make programmers more productive. Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.

And, from the Rust book:

Rust is for people who crave speed and stability in a language. By speed, we mean the speed of the programs that you can create with Rust and the speed at which Rust lets you write them. The Rust compiler’s checks ensure stability through feature additions and refactoring. This is in contrast to the brittle legacy code in languages without these checks, which developers are often afraid to modify. By striving for zero-cost abstractions, higher-level features that compile to lower-level code as fast as code written manually, Rust endeavors to make safe code be fast code as well.

Now we're starting to see some differences in objective. Go is designed to make it really fast to write Go code. It is supposed to be concise (so you type less) and quick to compile. It aims to feel like an interpreted language to work with. Meanwhile, Rust is preoccupied with delivering fast safety and stability. Meanwhile, Rust is looking to make higher-level abstractions as fast as large, manually-written, lower-level code. It's also preoccupied with safety and stability.

• These are two very different languages
• These two languages are solving two very different problems
• What attracted me to Rust is the error handling and borrow checker. You don't need a runtime and you don't need to worry about a variety of memory pitfalls.
• Rust is not just a systems-level language, and Go is not just a server-side language.
• Rust isn't *really* about speed or performance. It's about safety.
• Rust is just plainly a more powerful language.
• Go is for Python developers who need speed. Rust is for C++ developers who need safety.
• Rust has opt-in concurrent runtimes and opt-in garbage collection. These are standard in Go, there's no getting out of them.

Go has great concurrency. Goroutines are high-performance, parallel green threads. Rust's concurrency is provably-correct.

Why is the immediate question when someone says they wrote something in Go, " why not rust?". The inverse is true. When I tell a dev I wrote something in Rust, the immediate response is "you should have used Go, it's better." This is false.

What does suck about Rust? The compiler is slow. It will probably always be a degree of magnitude slower than another compiler for a similar target.

It's not Rust vs Go, it's when to use Rust and when to use Go. And the number one argument I get for why Go should be used is it's simpler and faster to learn and work with. There's the answer! The answer is use whichever one works best for you. There's no better or worse, or superiority. Redditors will say otherwise.

sources

Go vs Rust discussions are ridiculous. It should be more like: When to use Go. When to use Rust. When to use X… — Inanc Gumus (@inancgumus) September 19, 2019 source

Both Microsoft and Amazon have just recently announced and released their new officially supported Rust libraries for interacting with Windows and AWS. Official first party support for these massive APIs helps make Rust people's first choice when deciding what to use for their project.

quotables

Take a look Go as well. I think you will find Go much faster to program in. The other aspect is threading. They have very different threading models. Not sure if you had the chance to research that yet or not

Yes, a big thing is threading. Unfortunately, Rust uses a similar model as Java for threads :(. Go is based on Fibers approach which so much faster for temporary, lightweight requests. Go is definitely superior for HTTP REST API apps. Rust can be better for a single-thread app or general "systems" programming.

Rust is not a "systems programming" language. Systems programming is not a genre of languages. It's not like saying Italian is a "Romantic language". Systems programming is a specific, targeted programming *application*. It's the destination, the use-case that a language is being applied to. Rust is a general-purpose programming language. I have used it to write a variety of tools, low- and high-level, server-side and client-side, graphical and CLI. Yes, I used it for some systems programming. Also used it to make a very simple and robust web service digested by a variety of other developers at our company.

The only way is to learn and try both. That's what I did. Most of the info from both sides is biased...Go is definitely very fast and [garbage collection] is not the issue people make it out to be. I started last month porting [a chess] engine to Rust. I recently took a break from it because the syntax and borrow checking were getting insane to deal with. Once I learned about the threading issues in Rust, I have put it on the shelf for now. Rust is still evolving which is good and bad. It needs better IDE and Debugging support than current levels. Hopefully that will continue to improve. There was a big Mozilla shakeup (Nov 2020) where they let go of the Rust developers and cancelled the project. AWS hired them. So honestly, I am not sure which direction the language is going in. Meaning, now that AWS owns the braintrust, I don't know where they are headed. My guess is that AWS is using Rust for some behind the scenes script-like stuff. Not sure. Will be important in the next year or two on which direction things end up going. For Rust to benefit long-term, it needs the support of a corporate backer

IDE support? See rust language server, rust-analyzer, rustfmt, and cargo

Rust is absolutely ready for production use.

Anti-Rust zealotry is just as strong as pro-Rust zealotry. The hype goes both ways. No, your talking points shouldn't come from Reddit.

Everything isn't great in goland either. Gofmt and the go module structure were harsh and annoying for me to use. I don't prefer languages with rigorous whitespace requirements anyways. The opinionated standard library is fickler than I would imagine, and the drama churned up over the introduction of generics (a useful, modern programming concept) is popcorn-worthy

The hidden cost of Go: go might be faster to actually type in. But I spend much less time debugging in Rust. The compiler/borrow-checker tells me why I can't write to memory that's already been dropped or borrowed someplace else, and suggests what I need to paste in to fix it. These kinds of bugs take a long time to track down by stepping-through Go code. Some might not even get caught. I don't use a debugger for Rust because I rarely need to step through my code one line at a time to figure out where something became NULL

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x17cf291]

goroutine 52 [running]:
github.com/rclone/rclone/cmd/mountlib.(*MountPoint).Wait.func1.1()
	github.com/rclone/rclone/cmd/mountlib/mount.go:256 +0x51
sync.(*Once).doSlow(0xc00056c7f0, 0xc00057be38)
	sync/once.go:68 +0xb9
sync.(*Once).Do(...)
	sync/once.go:59
github.com/rclone/rclone/cmd/mountlib.(*MountPoint).Wait.func1()
	github.com/rclone/rclone/cmd/mountlib/mount.go:254 +0x59
github.com/rclone/rclone/lib/atexit.Run.func1()
	github.com/rclone/rclone/lib/atexit/atexit.go:104 +0x7f
sync.(*Once).doSlow(0x2e19420, 0x1e4ecd0)
	sync/once.go:68 +0xb9
sync.(*Once).Do(...)
	sync/once.go:59
github.com/rclone/rclone/lib/atexit.Run()
	github.com/rclone/rclone/lib/atexit/atexit.go:102 +0xac
github.com/rclone/rclone/lib/atexit.Register.func1.1()
	github.com/rclone/rclone/lib/atexit/atexit.go:52 +0xf0
created by github.com/rclone/rclone/lib/atexit.Register.func1
	github.com/rclone/rclone/lib/atexit/atexit.go:44 +0xa5