3 ms·

Why would you want to replace a "healthy" codebase?

• lostapathy 10y ago
  You wouldn't. I'm just observing that none of the CF I've had to deal with is healthy - it's all a mess they want to replace. Probably poor wording in my prior comment that was hard to parse as intended, apologies.
• askvictor 10y ago
  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