3 ms·
It's a delicate point, because on this one Joel is both right and wrong, depending on the circumstances. He's absolutely right that the "Big Rewrite" is a very
by swombat 18y ago
It's a delicate point, because on this one Joel is both right and wrong, depending on the circumstances. He's absolutely right that the "Big Rewrite" is a very dangerous proposition that should be assessed very carefully, but sometimes, it is the right choice.
I'll agree that in 95% of the cases it's not the right choice, though. We programmers do love us a good rewrite, even when it's bad for us. Incidentally, the Mozilla rewrite was probably in the 5% where it did make sense.
- lallysingh 18y agoI think a fair interpretation is if you have both conditions: 1. Is the whole code base a maintenance nightmare? 2. Do we have to change all of it right now? Which occurs, rarely. Most of the time a mechanical transform (e.g. Emacs macro) helps with the annoyances and standards. The rest, a deep refactoring is needed. Frankly, dumping the source and starting from scratch sounds a little like running away from your problems instead of attacking them head-on.