spidermonkey

Before, if you looked at all of an objects' properties in SpiderMonkey, you will have noticed an `@@iterator` property.

For anyone who wants to run Spidermonkey with Node, JXcore is a Node fork that enables this.

When running SpiderMonkey (interpreter, not JIT) on IA64 it would randomly crash and burn with what looked like GC issues.

Mozilla have done a lot of work to reduce the cost of that in SpiderMonkey.

You can use full GC in Rust--we use the SpiderMonkey GC to collect Rust DOM objects, for example.

Somehow rigging up spidermonkey to use a Nim-like GC in Rust (all other things being the same) would also be a bad idea.

Because rewriting Spidermonkey is both tedious and doesn't benefit from Rust safety guarantees.

If he was a mid level engineer working on Spidermonkey and got fired over a political contribution it would have been completely ridiculous.

Something close to that is already done with Servo's Spidermonkey GC integration.

If it adds an engine abstraction layer which would allow users to choose an engine (and somebody implements SpiderMonkey support there), sure why not.

SpiderMonkey's GC is very modern, it's not legacy at all.

There have been people working with Spidermonkey for ages.

"Nim's GC is better than Spidermonkey's" is a statement of no value (and oversimplifies the situation) unless the context is specified.

Unfortunately since it builds spidermonkey and some wrapper code it ruined any chance of "go get" working cleanly which doesn't make it a very attractive package.

Spidermonkey's GC is for GCing javascript, which already has an extensive runtime (which the GC ties into heavily).

Spidermonkey uses generational gc with some kind of compacting these days.

Nim's garbage collector is better than Spidermonkey's.