To take advantage of modern technologies? To be able to hire coders? That's two off the top of my head, I'm sure there are plenty of arguments both ways. Presu

To take advantage of modern technologies? To be able to hire coders? That's two off the top of my head, I'm sure there are plenty of arguments both ways. Presumably if your codebase is healthy, there is structure and documentation that would make it comparatively easy to replace in a different framework as requirements evolve. Unhealthy codebases don't have this so that stick around without adapting/evolving