Rust in 2026: rewrite or not?

This question doesn't come up during a retro, and it's not a joke. It comes up when the pain becomes too obvious. When production crashes again due to a segfault. When you've spent three days hunting down yet another concurrency bug. When a new developer looks at the codebase and says: "I have no idea what's going on here."

Rust solves specific problems. Memory safety, data races, low-level performance. That's why Amazon, Google, and Microsoft choose it. Not because it's trendy, but because it works.

But migrating to it only makes sense in one case: when you have a real problem that Rust can solve and your current stack can't.

Segfaults, memory leaks, complex multithreaded code, legacy that's impossible to maintain – that's when it's worth considering.

If your project is stable, brings in money, is written in something familiar, and your team doesn't know Rust – don't invent a problem that doesn't exist.

Rust is a tool for systems programming, not a silver bullet.

Anyone already made the switch? How did it go? Worth it or not?

And if you want to dive deeper – together with Evrone's DevRel Grigory Petrov, we wrote an article breaking down exactly when migrating to Rust is truly justified, and when it's better to leave well enough alone. Link here: https://evrone.com/blog/migrating-to-rust-in-2025