--nextPart3641909.e5s9Yf081I Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 07 October 2006 9:06, Andras Mantia wrote: > languages. For (a completely made up) example, I would oppose having > the clock applet for kicker written in Ruby/Python, but I don't oppose why? have you looked at styleclock? it is a c++ "shim" that loads kjs and=20 renders clocks written in js. in fact the clock is, imho, a perfect example= =20 of something that would be better done with scripting as it confers greater= =20 flexibility at very little cost to great benefit to the user. this is, btw, one of the reasons i advocate js over, say, python or ruby fo= r=20 these specific cases: the overhead is acceptable. > I think the basic desktop should work just fine without a need for a > language interpreter.=20 i don't think it's too much to ask for kjs or qsa. they are both lightweigh= t=20 and at least kjs is already in use on your desktop if you use konqi. it's n= ot=20 like the current clock written in c++ is exactly lightweight (it's one of t= he=20 fattest and certainly the slowest of all the default applets, actually) > Compiled code rulez. ;-)=20 for libraries and certain support roles, you bet. > If we are talking about complete applications written in a script > language, I'm fine with them, even shipped with KDE, if - again - they > do not provide basic desktop functionality. i do agree that it is good to keep the basic desktop as thin as possible. t= o=20 prevent scope creep by the compiled language bigots, i'd suggest that a goo= d=20 definition of "basic desktop functionality" would be required to make this = a=20 useful metric. and that's not as easy as it might sound ;)=20 =2D-=20 Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 =46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com) --nextPart3641909.e5s9Yf081I Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBFJ9jg1rcusafx20MRArFXAKCfToT+J2sF9m5ihr0TJ5UsPAt1LQCfWBj5 WzTzZcUSdzJ9S0deoXlcHgo= =VjIT -----END PGP SIGNATURE----- --nextPart3641909.e5s9Yf081I--