Linked by Thom Holwerda on Mon 26th Sep 2005 13:28 UTC, submitted by Malahide
Novell and Ximian "We chat to Gnome and coder Michael Meeks about all things Linux. Here's a few of the questions we asked the Novell employee."
Thread beginning with comment 36463
To read all comments associated with this story, please click here.
by Nex6 on Mon 26th Sep 2005 15:19 UTC
Member since:

He talks about KOffice startup in the interview and says KO has a shared start up using Kinit, and that OOo cant do that. so they are going to use Compiler stuff.

My guess is: thatOOo will slowly improve(startup) over time, but will always be slightly slow on start up.


Reply Score: 1

RE: Startup
by molnarcs on Mon 26th Sep 2005 22:56 in reply to "Startup"
molnarcs Member since:

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.

Reply Parent Score: 2

RE[2]: Startup
by Nex6 on Mon 26th Sep 2005 23:09 in reply to "Startup"
Nex6 Member since:

You are very correct, KDE's framework is light years ahead of both Gnome and OpenOffice, but that does not change the fact of OOo is slow or how to fix it.

I think over time OOo will get faster but abiword,kword and such will really be fast do to there better frameworks and smaller footprints.


Reply Parent Score: 1

RE[3]: Startup
by molnarcs on Tue 27th Sep 2005 12:10 in reply to "RE[2]: Startup"
molnarcs Member since:

Agreed. I can't wait for a koffice port to windows (not that I'm using windows - but it would be a good showcase for the potential).

oo.o startup time might get faster over time, but it seems to me (I might have missed something) that they relegate the problem to the compiler. Which means, that they can't or won't to a thing about it in their own code, except for making it compile with gcc 4.x, which has better c++ support. GCC 4's better c++ support will help all c++ projects, including koffice, so in relative terms, there won't be many improvements I guess.

Reply Parent Score: 1