Linked by Thom Holwerda on Mon 26th Sep 2005 13:28 UTC, submitted by Malahide
Thread beginning with comment 36722
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
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
More News »
Sponsored Links



Member since:
I think the point of the preloading argument (while flawed) does illustrate some points. Because of the OO structure with all the libs inline it pretty much has to load everything from disk on startup. Things are not reused enough.
Windows and KDE have a facility whereby components are loaded at startup (during idle cycles) after the desktop is loaded. MS Office, Internet Explorer and probably KOffice take advantage of this. OO doesn't. Some versions of Mozilla even used this on Windows, essentially preloading parts of the application ahead of time to speed startup.
Admittedly OO probably needs to modularize its code base (ala xorg) and strip out redundant libraries where systems already have them. However that takes time and effort.
Other considerations are of course toolkits, system load, desktop environments etc. All of which appear to have a part in application load times.
Personally (this could be just my opinion here) I think this is a pretty pointless argument. If your time was so valuable to you that you can't wait for an application to load what are you doing reading this forum, let alone posting.