News for hackers. Stuff that matters.
Re:We switched to Node.js: the good and the not so good by DoubleCluster on Tuesday January 15, 2013 @04:51AM (#5059475)
In my experience it's quite doable (with a good IDE) to refactor the working but messy code into something maintainable. It might take the same amount of time as a rewrite but you'll still have all the features and corner cases covered. Usually refactoring will be much faster though.
Re:We switched to Node.js: the good and the not so good by Peaker on Tuesday January 15, 2013 @08:35AM (#5059979)
I disagree. Incremental changes are not always capable of reaching point B from point A.

A large, extremely messy code-base can make even trivial changes unsafe, let alone large changes.

The effort required not only to figure out what point B is, but also how to safely reach it from point A is immense. Much much harder than a rewrite.

However, it is a very good idea to meticulously read the bad old code and write down a list of things it handles -- to make sure none of it is missed in the rewrite.