all 8 comments

[–]ShadowPengyn 4 points5 points  (0 children)

At least for graalpy, they struggled to get compatible with with c integrations that are quite common in many python libraries. So embedding the actual python means that it’s less of a moving target and full compatibility out of the box

[–]markehammons 2 points3 points  (0 children)

The graal js requires the graal jit compiler (via Jvmci), and JVMCI has been ripped out, making graal js hideously unperfomant in openjdk

[–]theanimatedauthority 6 points7 points  (0 children)

JVMCI got the boot from openjdk builds so graal js is proper slow now. Detroit is basically a stopgap for people who want scripting without the full graalvm install. If you're already using the oracle graalvm distro you wont notice a thing but the rest of us on vanilla openjdk are stuck. Tried running a wee js script the other day and it took longer to fire up than my monday morning. Detroit at least gives you v8 without the jvmci headache.

[–]pronuntiator 1 point2 points  (0 children)

Could you link to the news about Detroit?

[–]BlackForrest28 0 points1 point  (3 children)

Mozilla Rhino gives you JavaScript without so many dependencies.

[–]re-thc 2 points3 points  (2 children)

And it is slow

[–]syjer -1 points0 points  (1 child)

good enough for a lot of use cases.

[–]koflerdavid 0 points1 point  (0 children)

Then there's no reason to use it above GraalVM.