Linked by Thom Holwerda on Wed 29th Aug 2007 00:08 UTC, submitted by superstoned
"With an avalanche of last-minute commits, the KOffice Google Summer of Code students finished yet another great Summer of Code. We had some very exciting projects this year, and most of them were as great a success as last year. Read on for details of the achievements."
Thread beginning with comment 266446
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: What Koffice really needs...
by superstoned on Wed 29th Aug 2007 09:11
in reply to "What Koffice really needs..."
Member since:2005-07-07
Member since:
2005-09-28
Those guys have added some awesome looking stuff, and given the KDE framework and potential for integration, I think Koffice has the potential to be a winner.
However, what Koffice really needs is feature freeze and stability. Regardless of how many cool features are added, an office suite is unusable unless it is reliable and consistent. This is something that Koffice has yet to archive. And when I say this, I speak from my own experiences with it and with reference to the experience of others.
Frankly, Supercalc running on a 286 is generally of more use than a spreadsheet that crashes every few minutes.
This is a point that the Linux community needs to accept: an unreliable, inconsistent program is of no use for serious work. Perhaps, people who work in business could explain to their customers that there will be a delay because the program they use is conceptually very interesting, but in practical terms, nearly unusable.
Koffice looks great and has a lot of potential and want to dump Open Office and switch over, but I can't.