> Rewrites in general are usually a terrible idea, unless the original is horribly broken (and beyond fixable). I would say, it depends on the ROI. For exampl

> Rewrites in general are usually a terrible idea, unless the original is horribly broken (and beyond fixable). I would say, it depends on the ROI. For example, my current millstone, is a 20 year c++ program written towards the c++98 spec. The physical hardware is held together with spit and best wishes with the current management stating that we need to move to a Linux based, Intel platform as that's what 99% of the org is on. And, we're not licensing Vendor A or B's product, therefore "patch it till the major rewrite is completed". In the intervening 20 years, C++11, 17 or even 20 is very different from 98. Will I rewrite the whole thing, nope, as there's another project to rewrite the client/server portion (again 20 years ago) and at that time, I will eliminate that c++ piece.