Re: New Module Proposal. libseed

[Alberto Ruiz <aruiz gnome org>]

2009/5/13 Jason D. Clinton <me jasonclinton com>:
> On Mon, May 11, 2009 at 9:59 PM, Robert Carr <carrr rpi edu> wrote:
>> So far, Seed adoption is still somewhat light. Epiphany-webkit in GIT
>> contains a system for writing
>> extensions in Seed, which seems to be working fairly well. In addition
>> GNOME-games contains
>> lightsoff, a Clutter game written in Seed. Same GNOME is also likely
>> to be replaced with
>> something based off the same-seed example, over the 2.6.28 cycle (work
>> on GNOME-games and
>> Seed is occurring as part of
>> http://socghop.appspot.com/student_project/show/google/gsoc2009/gnome/t124022402774
>> ).
>
> +1 from me. Robert has been very responsive and his team of minions
> have made changes whenever I've asked.
>
> I think we must have both engines. The JS optimization battle between
> Mozilla and Apple is just now heating up; we cannot wait until the
> battle is over to pick a winner and start working with JavaScript.

That sounds to me more of a counter argument, is the GNOME official
desktop release the right place for a JavaScript engine battle? Isn't
the performance of both already good enough for our purposes? It seems
to me that they both already perform better than Python and we've been
supporting it for ages already.

It also seems to me that JSC/Seed is being adopted in much more
modules than GJS (please, correct me here if I'm wrong), plus there
are quite a few modules going for WebKit. I think that having one, and
only one choice for things like this (platform), are quite helpful in
order to have a more consistent platform.

Note taht Javascript can be a potential entry vector for the GNOME
platform (which is one of the most interesting points of getting a JS
engine in), I think people will have a hard time to make a decision
they might not fully understand (the engince choice), and
documentation will get messier. Not to mention that we will end up
with one extra dependency.

So I'm with Vincent here.

> Having JS with which we can:
>
> A) attract web developers to our platform with little relearning
> B) interface with myriad JS-driven web-apps-to-desktop-apps; think
> Mozilla Prism, Adobe AIR, HTML5, Google Gears
>
> is critical to our ability to adapt to the web-oriented marketplace.
>
> In summary: we need both engines and we need them in our platform
> sooner rather than later.
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
>



-- 
Un saludo,
Alberto Ruiz