OpenJDK is reviving the Detroit scripting engine with V8 for JavaScript and the native Python engine. What does that offer over Graal, and does it mean Graal will stop supporting those languages?
Why bring back Detroit when Graal already supports JavaScript and Python?
Asked by
bravely_unsure
Answers
One possible motivation is performance on a standard OpenJDK build. The discussion points to the removal of JVMCI from OpenJDK builds, which affects access to the Graal JIT compiler and can make Graal JavaScript considerably slower there.
Detroit could offer another route for embedding scripts without requiring a full GraalVM distribution. That does not, by itself, imply Graal JavaScript or GraalPy is going away.
Reply to this answer
For Python, native extension compatibility is another reason to consider it. Many Python libraries depend on C integrations, which can be difficult for an alternative Python implementation to support. Using the native Python engine may make those integrations less of a compatibility problem.
Reply to this answer
There are other JavaScript options too. Rhino is one if you want fewer dependencies, though performance is a commonly raised drawback. So the choice isn't just Detroit versus Graal.
Reply to this answer
Add your answer
Answers are reviewed before publication.
n62!sidefolder_407:
That distinction matters. The tradeoff may look different if you're already using a GraalVM distribution rather than a standard OpenJDK build.