Re: The future of binary embedding

On 3/1/2012 9:32 AM, [email protected] wrote:
> It seems that Luke has ended up in Ben's explicit or implicit killfile.
This thread is now way off-topic. It was originally an announcement 
about how we're removing *binary-stable* embedding APIs, and it has 
morphed into a discussion about the relative merits of pyxpcom, which 
didn't use these embedding APIs and was unaffected. We are all quite 
clear that pyxpcom clients don't have to worry about binary changes 
because they are insulated by pyxpcom middleware and have the benefits 
of being a scripted language.

However, pyxpcom has *never* been built or maintained as part of the 
regular Mozilla build/test infrastructure. It was originally in the CVS 
tree because that's where you put extension projects. It has since been 
moved into its own mercurial repository, and has a module owner, Todd 
Whiteman (ActiveState), and mailing list: 
http://listserv.activestate.com/mailman/listinfo/pyxpcom

As moderator of both the mozilla.dev.platform and mozilla.dev.embedding 
forums, I request that any further discussion about the future of 
pyxpcom and trying to build a community around it be moved to the 
pyxpcom mailing list; it is completely offtopic for the dev.platform 
list and has been thoroughly discussed in dev.embedding.

--BDS