Sam Cao
> > > > You might be interested in https://mikehearn.github.io/nodejvm/ which has an API and other utilities for synchronizing and scheduling work back and forth between NodeJS and Java. >...
It's been so long. I just submitted a fix to the dev branch. Do you mind taking a try? The snapshot build is at Actions.
Private Linux arm64 (experimental) is available, please ping me at discord if you want to have a try.
Linux arm64 will be supported from Javet v3. However Linux arm is another story as: 1. I don't have the hardware. 2. I expect someone to sponsor that work.
Please check this [doc](https://www.caoccao.com/Javet/tutorial/basic/installation.html) out. All versions are compatible with MacOS.
@davidekholm I wonder if you have evaluated some other V8 based solutions?
> @caoccao, no. What were you thinking of? Quite some Nashorn users who share the same concern with you eventually get onboard to a V8 based solution [Javet](https://github.com/caoccao/Javet) with significant...
I'm also interested in this _pooling_ design. As GraalJS GC is integrated with the JVM GC, does a GC of a specific ScriptEngine generate impacts to the rest of engines...
Thank @lemanschik for the detailed explanation. That confirms my concern: the script engines in GraalJS are not completely isolated as they share the same GC. In some critical situations, the...
Well, now the topic seems to move to AOT. I'm fine with everything changed/optimized in AOT, but JS interoperability is lost in AOT. In quite a lot of scenarios, JS...