Even so, there is the Netscape story as evidence to the contrary.
But (disclaimer) as someone who as advocated for big-bang-rewrite's before, I'm still under the impression that there are situations where they can be net-better.
Factors may include:
- there is no database involved, just code. Even more helpful if the existing code is "pure".
- a single developer can hold the functionality in their head.
- there are few bugs-as-features, tricky edge cases that must be backwards-compatibility, etc.
- as stated above, it's the primary author.
- much of the existing functionality is poor, and the path for building, launching, and shifting to a "replacement product" is relatively clear.
Advocating to never rewrite can be harmful, and make things harder for people for whom that actually would be the best approach.
But the situation that I'm describing is not ticking any of those boxes and I think I made that quite clear in the pre-amble.
Oh, there's no doubt in my mind about that!
Some people may read this and extrapolate too far regarding their own situation (there's a reason this is a specialty field, it's hard stuff).
That may not be true in this case, if the rewriter is also the original author and has remained active in the codebase over the years.