[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Using scripting languages for KDE4 main modules
From:       Luciano Montanaro <mikelima () cirulla ! net>
Date:       2006-10-03 13:29:23
Message-ID: 200610031529.23507.mikelima () cirulla ! net
[Download RAW message or body]

On Sunday 01 October 2006 20:40, Stephen Leaf wrote:
> On Sunday 01 October 2006 7:31 am, 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
> > and Ruby (at least we all agree that Perl is a no-go :-) ).
>
> not everyone, I hate the python syntax. And as for ruby syntax?.. I've
> seen scribbles that were more readable. Maybe it was just the examples on
> the official page I dunno but it just churned my stomach.
> I personally prefer Perl out of those 3 choices.
>

What is the state of Perl bindings? 

That aside, these languages are attractive in large part because of their 
large libraries, and the problem I see is not using the language on its 
own, but rather the huge dependecies it is likely to require.

Configuration panels are a good example of where scripting languages could 
be used, but do we want half of them written in Python and half in Ruby? 

Or could we use javascript instead?

Javascript is not a great language, but we already ship it, is easy enough 
to learn and it's small.

Luciano


-- 
./.. ../ /./. .. ./ /. ///   // /// /. / ./ /. ./ ./. /// ././. //
                                                            \\ //
                                             www.cirulla.net \x/
[prev in list] [next in list] [prev in thread] [next in thread]