Rust or Go

Any particular use case?

I've used both and prefer Rust, but Go is way easier to learn and get a MVP out.

This isn’t very helpful. I’m sure someone can weigh in on some thoughts here.

For different use cases you'll find each of them having a different set of benefits or shortcomings over the other, so knowing a bit about what you intend to do would make it easier to offer an informed opinion.

That being said, Rust is slightly harder to get into but a much better option than Go where basic things like error handling may feel incredibly backwards depending on how you view languages. Rust code has a reputation along the lines of "if it compiled then it works", which is always nice.

These kinds of discussion are seldom useful. Each language is a tool, and as such maybe there are use-cases in which each excels at, while the other "kinda sucks".
The question is not focused at all.
Besides, asking these kind of questions might result more in a war-of-religion (kind of) than a useful source of insights.

Maybe if you changed the post and described what you are trying to achieve, which level of understanding of expertise is expected, etc, you could get much useful material

Go is a terrible language, lacking a lot of ever basic features (e.g it has no error handling, no generics, no math functions for integers...). If you used any other language to it's full power before, you will notice it very quickly.

This might be helpful

Rust vs Go in Backend Web Development

Lane Wagner ・ Jul 20 ・ 3 min read

#go #languages #rust #compare

I personally prefer rust over go, cause first, u get better code completion in vscode,
second, you get very helpful hints from the compiler if u do something wrong.
third, list goes on and on