[Sugar-devel] python hulahop article

[Brendan Eich]

XPCOM is self-deprecating. It's excessively costly for both callers  
and implementors of its interfaces, both in runtime overhead and in  
expressiveness restrictions. We aren't going to drop it but we are  
already optimizing around it, and removing it in future APIs.

This doesn't mean multiple programming languages won't be able to call  
or implement those APIs. Cc'ing Benjamin Smedberg, who can say more.

/be

On Jul 27, 2009, at 7:34 AM, Luke Kenneth Casson Leighton wrote:

> On 7/27/09, Lucian Branescu <lucian.branescu at gmail.com> wrote:
>> I've even heard that the mozilla folks want to deprecate XPCOM, in
>> favour of more JavaScript usage in Firefox et all.
>
> that would be disastrously bad, cutting off all dynamic languages but
> javascript.  the declarative style which hulahop opened up (without
> realising it!) is _really_ promising.
>
> article's just gone up on mozdev (thanks todd)
>
>   http://pyxpcomext.mozdev.org/tutorials.html
>
>> 2009/7/26 Luke Kenneth Casson Leighton <lkcl at lkcl.net>:
>>
>>> what would be _especially_ good would be for xpcom to be "broken out
>>> of" xulrunner both in peoples' minds and also in actual real code.
>>> xpcom is a dumbed-down version of DCOM (i.e. with the D removed and
>>> many other features) and so i _know_ just how powerful it really is,
>>> but very few other people - outside of the mozilla community - are.
>>> which is a real surprise.
>>>
>>> you can register services as objects, and have them seamlessly
>>> communicate across programming language barriers... that kind of
>>> technology is just... gold dust!  the mozilla community should be
>>> raving their tits off about that!  and it's just weird that they're
>>> not doing that, whilst gobject is struggling to make ends meet.
>>>
>>> l.
>>
>>> _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>