Every team has the meeting. Someone says "we should rewrite it in Rust" and half the room nods and half pretends to check their phone.
Let me steelman both sides before the thread descends into the usual.
For. A large share of serious bugs in C and C++ code bases are memory-safety bugs: use-after-free, out-of-bounds, data races on shared state. Safe Rust rules those out by construction, at compile time, without a garbage collector. That is a real property, not a slogan.
Against. A rewrite throws away years of tested behaviour, including the weird edge cases nobody documented. It takes much longer than anyone estimates. The team may not know the language. And unsafe exists: wrapping a C library in Rust does not make the C safe.
My current view: do not rewrite, replace pieces. Pick the part with the worst bug history (usually the parser or the network-facing code), put a clean interface around it, and rewrite just that. Call it from the old code through FFI.
Counter-proposal, then: has anyone done a partial migration like this, and what went wrong?