Use whatever tool you can be productive in. Working software > early optimizations. End of thread. More on reddit.com

In my day job we have a mix of Ruby, JS and Go. I'm the only person on the team that knows Rust and I've occasionally toyed with the idea of introducing Rust to some of the other members. However, I don't think it's a good fit for our team. Go is just simpler. You have GC. You don't have generics. You don't have macros. You don't bang your head against the borrow checker. Don't get me wrong. I vastly prefer Rust to Go, but we have to hire other programmers. My management is not going to sit still as we got through several months of on-boarding of Rust concepts to new programmers. We have an education crisis in development. More than half of the people applying for jobs where I work have almost no formal education as programmers. At best they have 6 months in a boot camp and some real world experience. However, the real kicker is that generally speaking, those people are not much worse programmers than people with CS or engineering degrees. If our goals are producing competent programmers our university programmes are generally unsuitable. Rust just requires that you be fluent with a lot of concepts. I honestly feel that all of these concepts are the absolute basics of programming. To be frank most professional coders do not know the absolute basics of programming. Would I be better off hiring Rust programmers that understood a greater set of these basics and who were also proficient in Rust? Yes, I would. Would my management sit still while I looked for such people? Would my management be willing to pay for such people? No, they wouldn't. Which is not to say that my colleagues are unskilled, or incompetent. I'm lucky to work in a very, very good team. It's just that most of them are skilled in a very narrow set of skills. When we onboard new people, we similarly have to bring them up to that standard in a very short period of time. Keeping the set of required skills to a minimum helps a lot. More on reddit.com

Having used both, Go hides its complexity behind the veneer of simplicity while being more tedious and error prone as the codebase grows while Rust brings the complexity to you upfront while preventing errors later. Personally, even simply due to language features like algebraic data types ... More on news.ycombinator.com

Do you have one of the very few backend software usecases that need to work extremely close to the hardware, e.g. run a userspace filesystem driver? Rust.

Everything else in backend? Go.

More on reddit.com