> Should you replace your C codebase with Rust... or Go? Handy sanity tip: If your question begins "Should you replace your ____ codebase?", you can automatica

> Should you replace your C codebase with Rust... or Go? Handy sanity tip: If your question begins "Should you replace your ____ codebase?", you can automatically answer "No." If you're really starting to hate your codebase, you're allowed to rewrite one module using a new tech stack, but only if that tech stack seems uniquely well suited to the task at hand. Maybe it will suck. Maybe it won't. If it doesn't suck, you can use a bit more of the new technology in other places. This will lower your stress and give you an opportunity to futz around with something promising every now and then. As a strategy, it will probably work best if you occasionally enjoy new technologies, but you're conservative about what you're willing to use in production. It also helps if you have occasional throwaway open source projects for trying out stuff that looks too new for professional use.