b2evolution is actually an evolution of the b2 blog software. Thus, a significant part of the codebase is b2 legacy. As of today, b2 legacy is a little less than 50% of the whole b2evolution code.
Every now & then I read these quite irritating remarks about some other b2 forks supposedly being so much better because their authors are planning to rewrite it from ground up someday. :crazy: Duh!
Beyond the intrinsic irony of this statement, I'd like to explain my position about this: I do not believe the usage value of software lies in its codebase!
Actually, I have experimented the rewriting path myself about 12 years ago. I had developed a piece of software working very well with lots of happy users. However, I decided that having written this software in GfA Basic wasn't good enough and rewrote it from ground up in C!
This was an unvaluable move for me to learn the C language (and a couple of other things I wanted to experiment with, like the GEM environment), but regarding the software, the new version - while significantly nicer - never reached the usage value of the previous one.
The product and the users would have benefited much more from me spending all this time adding new features to the existing codebase instead of reimplementing the same ones differently. However, as a developer, I personnaly benefited more from reimplementation.
See how precisely this translates to b2 and its forks?
Now, please give me a break with this rewriting crap! Anyone talking to you about rewriting doesn't actually care about the community but about himself. :lalala: I don't blame that - we work for free - I just don't want it turned into ridiculous "marketing" arguments.
Also, please don't get me wrong: I am not saying the legacy b2 codebase was all clean. The b2evo dev team has actually rewritten more than 50% of it in order to achieve better maintainance. But we don't advertise that. We take far more pride in providing new features on a regular basis. :P