Re: Using Spidermonkey as a browser JS content back-end

Thank you both for providing some more clarification!

On Saturday, March 25, 2017 at 10:14:03 PM UTC+1, Jan de Mooij wrote:
> we have also made large
> architectural changes that required lots of changes to both SpiderMonkey
> and other parts of Gecko, and you can't easily backport these. Examples are
> the JSContext/JSRuntime unification (older branches use multiple contexts
[snip]
The contex/runtime issue alone would be a huge problem, indeed. I wasn't aware that you've unified that -- that would make it completely incompatible with the other back-end components we have. I guess that also explains why so much refactoring has been going on, although I got kind of numbed on that and stopped paying attention since so much of that was just busy-work and pointless renames; the actual work done got buried under all that fluff.

> either disable them or make a lot of platform changes. These are just a few
> things that come to mind but there are many more.

Yes, it looks like I'll have to re-think my approach here. Thanks for the insights!

MC