Glen Barrington
Forum Pro
My understanding is that there was an enormous amount of useless 'spaghetti code' remaining in the OO legacy code that ate up cpu cycles but did nothing and slowed down OO and made support rather difficult When Libre Office was branched off of Open Office, much of that useless code was trimmed. (Any programmer can tell you this is NOT an easy task, you can 'break' a lot of stuff if you aren't careful)
It made LO a tiny bit faster and slightly more responsive, but the real potential gain was in making changes easier. Clearly Apache would want to clean that up to remain competitive. When Apache took on OO, the speculation was that Apache had 2 big tasks.
It made LO a tiny bit faster and slightly more responsive, but the real potential gain was in making changes easier. Clearly Apache would want to clean that up to remain competitive. When Apache took on OO, the speculation was that Apache had 2 big tasks.
- Rebuild the supporting developers many of whom left for LO. Volunteer developers with the right skills and willingness to work for free don't grow on trees!
- Clean up the code in the way LO did, and restructure the code for growth.