Thanks to the efforts of its volunteer taskforce, over half the unused code in LibreOffice has been removed over the past six months. It's good to see this clean-up operation but it does raise questions about the amount of dead code lurking out there in the wild.
Carrying around unwanted and unused code is a real burden - it slows performance and makes code more difficult to maintain.
Michael Meeks, a longtime OpenOffice.org developer who is now one of the seven board members of The Document Foundation, has produced a graph that shows how the number of identified unused methods has dropped from nearly 5200 to around 2000.
It seems that over half of our unused code has now bitten the dust. Unfortunately as we remove more, more wastage tends to be revealed, which explains some of the upward jumps in the graph, nevertheless the trend is clearly down. One of the side benefits of the unsung heroes working at the conversion of our old-style macro driven generics to modern STL is that this loses us several unused methods per class converted.
Meeks points out that an unusedcode.easy file in LibreOffice lists methods that should be removed and suggests that joining this clean-up campaign is a good way to get involved with the LibreOffice project. He also recommends those working on other projects, to use the callcatcher method, developed by Caolan McNamara of RedHat, to identify unused methods lurking in their own code.
It is a worthy but sobering enterprise. To remove dead code is a good thing, but how can we have reached this point and seriously be discussing a situation where dead code is allowed to remain undetected and unremoved for so long?
The scale of the dead code in LibreOffice is shocking, and it probably isn't because the code base is especially bad. Can you imagine this in any other engineering discipline? Oh yes, we built the bridge but there are a few hundred unnecessary iron girders that we forgot to remove... Oh yes, we implemented the new chip but that area over there is just a few thousand transistors we no longer use... and so on.
It is just over a year since Google broke away from WebKit and decided to create its own version of the rendering engine just for Chrome. What is amazing is just how much benefit Chrome has accrued fr [ ... ]