I think rewriting is a great option, provided both options are weighed up appropriately.
However saying this, we made the decision to rewrite a legacy system around a year ago and the project got parked due to "urgent" projects being fed to our team. This was frustrating but we could not account for this external factor when weighing up the options.
I think changing priorities is a risk that has to be taken into account whenever you are considering any task that will extend for a long time -- rewriting code is just one example.
If you have to go on for many weeks / months on a project without the possibility of showing intermediate results, it is naive not to think that there is a high risk of the project being cancelled.
Location: Nottingham, UK
Remote: Yes
Willing to relocate: No
Technologies: strong - C#, .NET Core, Javascript, React,
SQL Server, Server Admin, Azure, Azure DevOps,
Architecture
Résumé/CV: Available upon request (6 years exp)
Email: rjdeveloper30@gmail.com
However saying this, we made the decision to rewrite a legacy system around a year ago and the project got parked due to "urgent" projects being fed to our team. This was frustrating but we could not account for this external factor when weighing up the options.