--nextPart1383849.aDIsO1h7Lh
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 01 October 2006 08:31, Guillaume Laurent wrote:
> On Sunday 01 October 2006 13:00, Alexander Neundorf wrote:
> > I don't think it would be possible to reach a consensus on this one:
> > python <-> ruby <-> java <-> c# ...
>
> We want a script language, so Java and C# are out of consideration, the
> added value compared to C++ just isn't worth it. So it's between Python a=
nd
> Ruby (at least we all agree that Perl is a no-go :-) ).
>

Why? I've been writing perl-qt / perl-kde for a while now in KDE 3.5 and wo=
uld=20
not card to have to move to another language when the time comes to move to=
=20
KDE 4. I know that the bindings for perl need work to get them working with=
=20
KDE 4, but that doesn't preclude it from building applications against for=
=20
the current 3.5 series atm.
=20
> My own preference would be toward Ruby, but I think the safe choice would
> be Python, because of its "there's only one way to do it" syntax.

Personally, I think this idea of selecting an "official" application script=
ing=20
language is a bad idea, as that again raises the bar for new developers.

--nextPart1383849.aDIsO1h7Lh
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.9.20 (GNU/Linux)

iD8DBQBFIpEbCkngzK11zHsRAiVUAJ9MjozrWsHHms0YdKK9P4EOR2cr2QCfcV1m
2xxzH2fGeI2wU7cY9nkYRZI=
=HNlR
-----END PGP SIGNATURE-----

--nextPart1383849.aDIsO1h7Lh--