First, it’s very important to say that both Go and Rust are absolutely excellent programming languages. My purpose here is not to criticise any language
In this article, I’ll try to give a brief overview of where I think Rust is the ideal choice, and where I think Go is a better alternative.
If you had to sit down and think of the programming languages which were best aligned with the motive to develop secure, microservice favoring frameworks and apps, you would again find yourself staring at the two languages.
Even after being similar in some prominent ways like maturity, being open source, and being designed for microservice oriented, modern, parallel computing environments, there is a lot of confusion around Go vs Rust and which of the two languages are good for the developer community to enter into.
Let’s think you mainly works with Go and you bulid some too which works great. You claim that since you wrote it in Go, it’s fairly fast, it’s a single binary, etc. You share this with a group of people seems pleased with your claim and you start feeling amused, but then you notice someone approaches you and shout: “Why Go over Rust?”
You start to feel overwhelmed. Well, you could answer that Go is what you know, so that’s what you used to solve your problem, but that’s probably not going to…
