Join the DZone community and get the full member experience.Join For Free
Akka from A to Z, An Architects Guide starting off with Actors and Akka Streams, then on to clustering, sharding, event sourcing & CQRS, and more.
We spoke to Henrik Stahl, senior director of Java product management at Oracle to find out more.
DZone: Where did the motivation for Nashorn come from?
Henrik Stahl: Oracle recognizes that multi-language support is important to Java
- The Rhino engine currently used is dated and not architected together with the JVM
DZone: How long have Oracle been working on it internally?
Henrik: We have been working on Nashorn for the past year and a half.
DZone: Was it originally for any other purpose or products?
DZone: How much of Nashorn is already complete?
Henrik: The Nashorn engine is passing all ECMAScript 5.1 compliance tests. Early access users have been able to switch their application from Rhino to Nashorn without major issues.
DZone: And what still needs to be added?
Henrik: The team is currently focused on robustness and performance as well continuing to evaluate potential JVM optimizations. The team is also starting to explore support for upcoming ECMAScript 6.0 features.
DZone: Why do you think that Nashorn will be more successful than Rhino, the previous JS implementation on the JVM?
- Nashorn significantly outperforms Rhino, and the gap will increase even more as we now move focus from spec compliance and stability to performance
Opinions expressed by DZone contributors are their own.