--nextPart50290120.C41RFKabxW Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 27 March 2008, Luciano Montanaro wrote: > This is not a problem for your typical, current, desktop PC. But many > linux-friendly devices are being deployed where memory and disk space are > limited resources (the Classmate, the Eee PC... more models seem on their > way), the first gen EEE PC comes with python on it already; the next generation=20 devices will have even more storage. so these really aren't the devices tha= t=20 we need to be worried about here. when we're talking about "can we fit a=20 python interpreter" on it, we're talking small devices like phones,=20 ultraportable tablets, blackberries, etc.. > so, while I agree that having interpreted code for settings and=20 > rarely executed programs is a valid choice, I'd rather at least have one > "blessed" language for this kind of modules. honestly, a bigger real world problem here is fitting these dialogs on the= =20 screen size of these devices. as you get to small devices, i find that thin= gs=20 like guidance run out of screen space first ;) > That may be Python, or something else... I'd prefer one of the ecmascript > interpreters we ship, actually... for in-application scripting, absolutely. for full apps, something with mor= e=20 available libraries, more application dev appropriate docs, etc would be=20 nice. in fact, many of the things that make ecmascript really great for in= =20 application scripting are hindrances for full app devel ime. > It would be nice if we had one javascript interpreters instead of two-- > soon three, but that's another problem. a third? oi.. whre's this? =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Trolltech --nextPart50290120.C41RFKabxW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBH7LDc1rcusafx20MRAsv+AJ49o8/s/L81O9qL0R2ZzV+xTJ07lQCeLvQv mJVZTcq0yT0jOxhRvhk2HvQ= =4BhD -----END PGP SIGNATURE----- --nextPart50290120.C41RFKabxW--