GraalVM Forking existing Runtimes vs Implementing the Minimal Needed Runtime in Java

[frank-dspeed]

GraalVM Forking existing Runtimes vs Implementing the Minimal Needed Runtime in Java

At present the GraalVM Team focuses on Integration of existing Runtimes into the GraalVM Ecosystem via minimal Patching and Optimization of the LLVM integration of the C parts of that Runtimes

I my self out of the View of a ECMAScript Runtime Implementor that works on many Implementations like NodeJS and Deno as also Many others got a other view about that.

I Think it is more fast and even better as it allows Runtime Costumasation to Implement the Standards of the Runtimes in Java Directly with already existing Java Code.

for example the FS Module from NodeJS Could easy be java.nio and so on same for other Runtimes and other Languages. Adopting the Changes of the C Code is not logical to me. But i need ways to Prove that as only one Solution at present exists and thats the One where the C code gets reused. graalvm-node and graalvm-node-context are projects that should prove in Benchmarks that they are faster then the node-graal runtime