Linked by Thom Holwerda on Mon 26th Sep 2005 13:28 UTC, submitted by Malahide
Thread beginning with comment 36658
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
Linked by Thom Holwerda on 05/15/13 21:46 UTC
More News »
Sponsored Links



Member since:
2005-09-10
All I see that he uses the question of slow oo.o startup times to make a pass at KDE - I thought it is only us, users who like to flame one DE over the other based on our personal preferences.
What he says about kdeinit doing all the heavy lifting during kde/koffice startup doesn't hold water. Start up fluxbox, then run kword from a console - and it will load in half the time oo does. That's because of KDE's brilliant architecture and code quality. Kword loads fast because koffice, just like the rest of KDE, is component based and very modular - which makes the code not only more approachable but more maintainable as well. As a result, kword loads only the text editing component - and loads other components as you need them. Because these are smaller chunks, you want notice any lag during operation.