Standalone Nashorn 15.0 is out • Hacker News Board

Re: Standalone Nashorn 15.0 is out

#31

Post by blackmagicjs » Mon, Nov 30, 2020, 8:02 AM UTC

hansjorg wrote: post #13

Hasn't Nashorn been superseded by GraalJS? Is this just for those who are stuck with Nashorn, or will there be new development? GraalJS is ECMASCript 2020 compatible and is said to rival V8 on performance, so I would've thought it the obvious choice for new projects going forward. https://github.com/graalvm/graaljs Edit: found more info about this release in the initial announcement: https://mail.openjdk.java.net/pip…

Is GraalJS just an interface to NodeJS, or why do they mention the NodeJS API?

Re: Standalone Nashorn 15.0 is out

#32

Post by augustl » Mon, Nov 30, 2020, 8:07 AM UTC

blackmagicjs wrote: post #31

hansjorg wrote: post #13

Hasn't Nashorn been superseded by GraalJS? Is this just for those who are stuck with Nashorn, or will there be new development? GraalJS is ECMASCript 2020 compatible and is said to rival V8 on performance, so I would've thought it the obvious choice for new projects going forward. https://github.com/graalvm/graaljs Edit: found more info about this release in the initial announcement: https://mail.openjdk.java.net/pip…

Is GraalJS just an interface to NodeJS, or why do they mention the NodeJS API?

They have both. GraalJS itself is just a JS runtime, but they've also made a separate package that reimplements the Node stdlib (but doesn't work on Windows yet, for example)

Re: Standalone Nashorn 15.0 is out

#33

Post by blackmagicjs » Mon, Nov 30, 2020, 8:26 AM UTC

augustl wrote: post #32

blackmagicjs wrote: post #31

Earlier quoted context omitted.

Is GraalJS just an interface to NodeJS, or why do they mention the NodeJS API?

They have both. GraalJS itself is just a JS runtime, but they've also made a separate package that reimplements the Node stdlib (but doesn't work on Windows yet, for example)

Good to know, thanks!

Re: Standalone Nashorn 15.0 is out

#34

Post by samus » Mon, Nov 30, 2020, 11:47 AM UTC

billfruit wrote: post #4

kasperni wrote: post #3

Earlier quoted context omitted.

To add to that. It was previously included directly in the JDK but is now a standalone product.

Why do they keep doing that, it makes dependecy management etc, more complicated. Sometime ago they did that with JavaFx, while still retaining AWT as part of JDK: what a baffling move, discard the best GUI framework on the platform, while including the most obsolete one.

These project operate at a much different pace than the JDK. Actually, it makes everyones life easier: any sane project at scale already uses a dependency management tool, and it's just another entry there. Also, it makes it possible to nail down the JavaFX version that is used. It's one moving target less that varies by JRE version at deployment time and can ruin the show.

Re: Standalone Nashorn 15.0 is out

#35

Post by needusername » Mon, Nov 30, 2020, 6:18 PM UTC

hansjorg wrote: post #13

Hasn't Nashorn been superseded by GraalJS? Is this just for those who are stuck with Nashorn, or will there be new development? GraalJS is ECMASCript 2020 compatible and is said to rival V8 on performance, so I would've thought it the obvious choice for new projects going forward. https://github.com/graalvm/graaljs Edit: found more info about this release in the initial announcement: https://mail.openjdk.java.net/pip…

> Hasn't Nashorn been superseded by GraalJS?

It depends, do you want support for your JVM? If so:

* Graal CE has no support

* Graal EE requires either running on Oracle Cloud or calling Oracle Sales for a custom quote. These are non-starters for many.

* JVMCI requires `-XX:+UnlockExperimentalVMOptions` which often voids support.

* I believe Mandrel is supported but requires RHEL