Re: Why so many??

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Why so many??
by jospoortvliet on Thursday 08/May/2008, @22:47

OpenOffice doesn't seem capable of ever growing beyond the 'copy MS Office 97' paradigm. It's codebase is too complex and dazzling to attract new developers, hence innovation is unlikely. KOffice, on the other hand, has a strong base to build upon, and is already doing a lot of interesting things. As I'm a strong believer in innovation as the way forward for FOSS, the chances of KOffice 'saving' the office workspace for FOSS are imho much larger than for OO.o.

Related Links

·   Articles on KDE Office Suite
·   Also by jospoortvliet
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Why so many??
by André on Friday 09/May/2008, @07:46

While I agree with you in theory, judging by the always existing lack of developers in KOffice, the simplicity and structure of it's code base (at least, relative to OO.o) does not really help in practice to attract new developers. Or am I off in this respect?

[ Reply To This | View ]

Re: Why so many??
by Amadeo on Friday 09/May/2008, @08:10

KOffice has far more volunteer coders than openoffice. What will happen if Sun stops funding openoffice? How many paid developers are required just to maintain it?

KOffice, with a clean and lean code base could save the day in that situation. just look what happened to KHTML x Mozilla.

[ Reply To This | View ]

Volunteers
by T. J. Brumfield on Friday 09/May/2008, @10:01

I think OOo lacks volunteers because Sun demands to own the copyright for all submissions, but they do have people like Sun, IBM and Novell paying a decent sized staff to work on OOo.

[ Reply To This | View ]

Re: Why so many??
by she on Friday 09/May/2008, @09:06

'does not really help in practice to attract new developers. '

I dont agree really.

Besides the problem is really that openoffice is an artificial effort right now, marketed by Sun.

Koffice is MUCH more close to the community.

The only problem is that I cant code in C++ (and I wont. I use ruby for all my work). :)

The best solution would be to be as generic as possible and allow people to write plugins etc.. in the language they use. I really have no need for java, c++ or whatever anymore, and I dont want to waste time just for coding in C++ (because I know, I wouldnt code in C++ anyway.).

[ Reply To This | View ]

Re: Why so many??
by Cyrille Berger on Saturday 10/May/2008, @00:28

Well actually with the Kross binding, you can write features in Ruby, Python and JavaScript, either scripts or even dockers. I don't know what you are intersted in doing, but you can do stuff in ruby, and we would really love to have some inputs on the bindings.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"If you have an itch not being scratched, you can scratch it, or pay someone to scratch it for you." -- Eric Laffoon
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.