>>104432471
>Is it time for us to migrate to Rust?
Do you have an estimate how long that would take for that large C++ codebase? How many new user-visible features would have to not be developed because of the porting effort? Do you think your management will be OK with this?
Unless you're very very lucky (or unlucky), codebases on the order of a million lines of code end up being codebases on the order of a million lines of code when ported to another language. This rule of thumb holds between quite different languages. Writing that much code takes quite a long time and a lot of work (and no, AI won't help at that scale; it can't scale up anywhere close to reliably). All that work means you pay a very large opportunity penalty: all the things that you're not doing but could have otherwise been doing.

tl;dr: if you can do it piecemeal then maybe, otherwise it's dumb and will cause you to lose your job

Back | Go to board

Board:

/g/

Thread:

>had to fix memory leak in the multithread setting in our big C++ codebase in the companyIs it time for us to migrate to Rust?

>had to fix memory leak in the multithread setting in our big C++ codebase in the company
Is it time for us to migrate to Rust?