To view parent comment, click here.
To read all comments associated with this story, please click here.
That's really not the point now is it... according to the idea that we don't need more choice, then OpenOffice, which has a code base much older than KOffice, should be the only one that needs furthering and the KOffice devels should just go ahead and contribute to the OO.org development. This is the way I feel about the people screaming "Why don't they just work together?"
JRM7
Apparently, you don't seem to be very aware of the situation in OO.o. The code there is almost a decade old and the code base is almost unmaintainable due to its large size.
Even though there are many groups contributing to the auxiliary projects (translations etc.) around OO.o, there are very few outside developers contributing code to OO.o and this is the reason.
KOffice has a much cleaner API, unlike OO.o and is much easier to hack on. OO.o will need to modularize its code base and eliminate even more outdated code before they can get community contributions flowing in.
Don't want to sound to Zen but I think you see my point even if you missed it the first time around. I wasn't saying that KOffice was worse off than OO.org. My whole point is that without the different projects we would be stuck with one or two things.
If we take the mentality that they should just work together and not have their separate projects, we are worse off.
Maybe I failed to insert enough sarcasm into my original statement.... I am too dry at times.
JRM7




Member since:
2005-07-08
Or Koffice when OpenOffice is already there?
Because koffice was there before openoffice was opensourced...?