lists.kde.org: Regarding 'osOpinion: The GNOME Ascendant' (A discussion of component architecture)Aug 26, 2000, 02:34 (34 Talkback[s])
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
[ Thanks to Katie the KDE Dragon for this link. ]
"...Whenever a performant and lightweight communication is required, shared library components, languange dependend and toolkit dependend, are chosen (in KDE). This provides a maximum of performance while eating as few resources as possible, and in addition it provides an _extremly_ powerful object model. An object model every average KDE/Qt developer is already familar with! The Qt object model. This means people don't have to learn yet another big technology (like CORBA in fact is, and CORBA is complicated) in order to make their hacked-in-their-free-time- small-application communicate with other components on the desktop."
"A classical examples here are:
"For these examples performance and resources are more important than stuff like network transparency. Noone is going to embed a remote spreadsheet document into a word document, running on a machine on the other side of the ocean. This is a nice dream and it is certainly technically interesting (no doubt about that), but it is not what the average desktop user really wants. The priorities are different here."
0 Talkback[s] (click to add your comment)