Stability is not MICO's fault. It's the general problem of stability/reliability in a distributed system. You have to add tons of handle-the-worst-case-of-network-failure exception handling to your code, which makes it bloaty and unreadable. And well, who needs that on the desktop? (it's still K Desktop Environment and not K Distributed Environment:-) A good paper about the reliability issues can be found here: http://www.sun.com/tech/techrep/1994/smli_tr-94-29 .pdf
Yeah, if the script would automatically write a mail to all authors, asking them for permission of changing the license text, waiting for reply mails, grepping for "OK", patch the text and then system( "cvs commit" );-)
Seriously, IMHO that's complete nonsense.
And I wonder when the debian guys will learn to accept additional opensource licenses, other than the GPL, given the fact that the QPL is just the same for opensource applications.
Re:Have they made it more light weight???
on
KDE 1.90 (2.0 Beta)
·
· Score: 1
hehe, how can you compare a desktop environment, which consists of many components, with one single window manager process?;-)
The difference is: Konqueror is seamlessly integrated into KDE, while not having that evil dependency. You can use KDE without konqueror. You can use konqueror from within GNOME You can use konqueror without KDE You can use Unix without konqueror;-) See?:)
>Great! YAWC (Yet Another Windows Clone). When are >we going to get a desktop for Linux that doesn't >appear to have come from the Microsoft school of >GUI design? I mean come on, it's nice to have a >GUI and all that rather than using console-based >tools with obscure command-line parameters, but >what does KDE offer that my Win2K box doesn't?
What KDE does offer?
a) it is *FREE* software (unlike w2k) b) you can COMPLETELY *customize* your desktop environment (unlike w2k) c) it is stable:-)
Slashdot Mirror
Stability is not MICO's fault. It's the general problem of stability/reliability in a distributed system. You have to add tons of handle-the-worst-case-of-network-failure exception handling to your code, which makes it bloaty and unreadable. And well, who needs that on the desktop? (it's still K Desktop Environment and not K Distributed Environment :-) A good paper about the reliability issues can be found here: http://www.sun.com/tech/techrep/1994/smli_tr-94-29 .pdf
Yeah, if the script would automatically write a mail to all authors, asking them for permission of changing the license text, waiting for reply mails, grepping for "OK", patch the text and then system( "cvs commit" ) ;-)
Seriously, IMHO that's complete nonsense.
And I wonder when the debian guys will learn to accept additional opensource licenses, other than the GPL, given the fact that the QPL is just the same for opensource applications.
hehe, how can you compare a desktop environment, which consists of many components, with one single window manager process? ;-)
all kdelibs stuff is under LGPL. kde apps are GPL. There are some exceptions, like some MIT, BSD and Artistic licensed components.
ugh, these are horribly outdated ;-) . We should make some fresh ones :-)
The difference is: Konqueror is seamlessly integrated into KDE, while not having that evil dependency. You can use KDE without konqueror. You can use konqueror from within GNOME You can use konqueror without KDE You can use Unix without konqueror ;-) See? :)
>Great! YAWC (Yet Another Windows Clone). When are >we going to get a desktop for Linux that doesn't >appear to have come from the Microsoft school of >GUI design? I mean come on, it's nice to have a >GUI and all that rather than using console-based >tools with obscure command-line parameters, but >what does KDE offer that my Win2K box doesn't?
:-)
What KDE does offer?
a) it is *FREE* software (unlike w2k)
b) you can COMPLETELY *customize* your desktop environment (unlike w2k)
c) it is stable