KOffice Team: A Handful of Coders, a Lot of Code
nickbrown writes: "In this interview with the KOffice development team it is revealed that only about 4-6 people are working on the suite of applications. It would appear they lack the resources to keep up with the likes of openoffice.
Worth a read as it highlights the troubles they are having trying to produce a truly productive office suite for KDE."
...open source tactics.
I mean, like, really.
Why don't open source coders collaborate more? Why in the hell do we need a half dozen different office suites?? Give me one good implementation, and that's all I'll ever use. Is it just that getting geeks to cooperate is like trying to get a group of 3 yr olds (or cats) to all go in the same direction -- near to impossible??
So concentrate on the applications that your average person needs, and accept that OpenOffice is going to be the heavyweight Office suite.
Make a flat file database program for people to store various bits of data. Make a word processor that can be used to write good looking letters and documents, but not have the more business features of Word. Make a spreadsheet that can be used to help calculate taxes or the monthly bills.
This is the real way open source works. Everyone cries and screams about open source, but when the rubber hits the road only a couple of people do a decent job and do the actual work, while the rest of the people just rave on about how l33t an open source coder they are. Most programmers expound open source... then try and figure out ways to sneak the code into their own stuff to make money.
This IMHO is the only way Linux will eventually 'win' within our lifetimes.
Their are so many projects which essentially do exactly the same thing, with no real difference or benefit (other than perhaps the choice of window enviroment they use). I personally think thats alot of wasted effort. Some unification would easily stomp MicroSoft but atm that doesnt seem to be the nature of Linux.
Also as for 'Linux conquering the desktop', it 'ain't never gonna happen'! The nearest thing youll get is 'GNOME conquering the desktop' or 'KDE'. It will be irrelevent what kernel its on as that probably wont effect its use.
Im not saying merge BSD/Linux/Herd thats madness :) But I feel some unification on the desktop side of things would only be beneficial to Linux
I know everyone likes choices, but if you encorperate the options into the Office suite/Desktop environment then you still retain your choice
Have you ever tried Konqueror? The best browser for Linux, and probably better than IE, making it the best altogether.
Save a webpage on your hard drive for future reference, load it in Konqueror, click a link on it and presto, your LOCAL file-path (file:/home/eyal/projectomega/ref.html) is sent as HTTP-REFERER to the webserver. No other browser does that. This tells a lot about how much KDE developers care about your privacy.
Koffice is pretty damn good as is... but unfortunately, there are some major insufficiencies: notably, filter support. I think most people who have actually tried using staroffice/openoffice would agree that there is a lot of unnecessary bloat. Another problem, for KDE-zealots like myself, is that other office suites don't integrate well into the slick, advanced, well supported, and popular KDE.
It just seems that with all the different projects out there that are supported by thousands of developers... there are only a few people for each that actually use the program. However, I see K-Office getting a lot more usage. It just seems that you get a LOT more *useful* code by improving k-office than by improving xyz-random project on Freshmeat. (my 2 cents)
The article says:
When you get down to it, an office product is really just a collection of different objects that have defined rules for interacting with eachother. You don't have to read all 350,000 lines of code to find a starting point for a new module.It takes a very long time just to reverse engineer other file formats and build filters.
The article confirms your point on the filters. They mention the filters as the one area where they need the most help. It would be nice to live in the ideal world where the producers of file formats create cleaner documentation, or provide industry standard filters for their formats that you can integrate in a product. Unfortunately, the temptation is to use poorly documented, proprietary formats to create a monopoly position in the market.
I didn't say small groups can handle all projects, just that they can do some things very well. I would agree with the article that filters are a rough edge.
The article incorrectly stated that Aethera was not being worked on, and that the last beta was in april of 2001; in fact, there have been at least two betas that I know of, just in 2002. And Kivio is not only being worked on but is supported under windows as well, in the commercial version.