Standalone Nashorn 15.0 is out
mail.openjdk.java.net
Standalone Nashorn 15.0 is out
1–10 of 35 posts
Re: Standalone Nashorn 15.0 is out
#2For anyone else wondering what Nashorn is:
It is Javascript running in the JVM
https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
Re: Standalone Nashorn 15.0 is out
#3For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
To add to that. It was previously included directly in the JDK but is now a standalone product.
Re: Standalone Nashorn 15.0 is out
#4For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
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.
Re: Standalone Nashorn 15.0 is out
#5For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
And it's stuck on ES5 from 2009.
Re: Standalone Nashorn 15.0 is out
#6Earlier 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.
It wasn't discarded, just delivered separately. Unlike Swing/AWT, JavaFX is not part of the Java SE standard, so vendors don't have to include it, but users can use it like any library.
Re: Standalone Nashorn 15.0 is out
#7For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
“According to Oracle benchmarks, Nashorn performance is several orders of magnitude faster than the alternative Rhino JavaScript engine.”
Interesting
Re: Standalone Nashorn 15.0 is out
#8Earlier 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.
Burdening all five users of FX or Nashorn with the one time act of dependency management setup is a much lower cost for java popularity than burdening all other users of java with the repeated minor annoyance of JRE bloat. As a bonus, both have a much better chance of seeing continued development outside of the stifling rigidness of the JRE development process.
Re: Standalone Nashorn 15.0 is out
#9For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
“According to Oracle benchmarks, Nashorn performance is several orders of magnitude faster than the alternative Rhino JavaScript engine.” Interesting
I might be wrong but this sounds a lot like you should be wondering what Rhino was (or is, apparently it's still not quite dead yet)
Re: Standalone Nashorn 15.0 is out
#10For anyone else wondering what Nashorn is: It is Javascript running in the JVM https://en.wikipedia.org/wiki/Nashorn_(JavaScript_engine)
“According to Oracle benchmarks, Nashorn performance is several orders of magnitude faster than the alternative Rhino JavaScript engine.” Interesting
> Nashorn performance is several orders of magnitude faster than the alternative Rhino JavaScript engine
...and several orders of magnitude slower than the other alternative JavaScript engine, GraalJS, which they don't mention for some reason.