Linked by Thom Holwerda on Sun 14th Jan 2007 23:05 UTC, submitted by an Anonymous Reader
KDE This week's KDE Commit Digest tells about an installer for KDE on Windows and the problems the developers encountered setting up a working environment for KDE to run on. Many screenshots included, showing the first applications (such as Konqueror) running natively.
Permalink for comment 201868
To read all comments associated with this story, please click here.
Member since:

How is clicking "Next" several times and watching a gague bar (several times for multiple applications) simpler than typing one command (one command even for multiple applications)? I don't want to click the buttons, I want my app! ;) .

Besides, static linking means:
a) size on disk - OK, disk is cheap
b) size in RAM
- there's never enough RAM
- the more RAM is available for caches the better
- no sharing of the same library code in RAM

c) size during transfer - bandwidth is _NOT_ cheap everywhere
d) security patches - oh yeah, let's download the whole huge static OOo binary instead of just libjpeg. and let's do it for all apps, that use libjpeg.

That's just stupid.

Granted, in Windows world, it works like that. However, that does not mean that it is a good thing to do.

Reply Parent Score: 5