On 2016-04-14 12:08 PM, Steve Fink wrote: > On 04/14/2016 06:21 AM, Philip Chee wrote: >> On 12/04/2016 19:27, Henri Sivonen wrote: >> >>> My understanding is that >>> https://git.merproject.org/mer-core/qtmozembed/ still uses it. As we >>> are figuring out how to be more embeddable (see >>> https://medium.com/@david_bryant/embed-everything-9aeff6911da0 ), it's >> AFAICT Spidernode is an ex-parrot. However the JXCore fork of Node.js >> can optionally use SpiderMonkey as their JavaScript engine. I wonder if >> the JXCore people would be willing to upstream their changes back to >> Mozilla? > > There's a new spidernode now -- <https://github.com/mozilla/spidernode>. > But it's much less complete than JXCore. Sadly, JXCore has itself been > discontinued, but the source was released under an MIT-style license at > <https://github.com/jxcore/jxcore>.
JXCore is a rewritten Node implementation which replaces all of the calls into the v8 APIs with Macros that are implemented differently for each backend that it supports, which is a very different approach than the one we're taking in SpiderNode. > Neither makes any changes to SpiderMonkey afaik; the changes that could > be upstreamed are to the Node source. There isn't really anything in JXCore that can be upstreamed anywhere. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
