JavaOne 2014: Takeaways from Java's biggest conference
A comprehensive collection of articles, videos and more, hand-picked by our editors
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Better performance and security
Laskey said that Rhino contained some cruft because it had been around since 1995. Hackers looking for vulnerable classes for security cases that had not been considered when Rhino was released could find them in Rhino. Secure frames in Nashorn's stack help limit the kind of classes that hackers have access to.
Getting the most from multiple threads
The LinkedIn developer also noted that performance is a little slow when an application is first warming up. Laskey said that the current version of Nashorn has some limits on code caching, which were not implemented for safety reasons. The team did not want developers to rely too heavily on this kind of capability until the bugs have been worked out. There are concerns about some of the possible side effects around clearing the cache over long periods of time.
Input, benchmarks and stories encouraged
A lead developer for Parse noted that many development shops are starting to leverage NodeJS, and he believes that Nashorn may provide a viable option for organizations that want an architecture that is better integrated with Java.
Developers interested in better understanding some of the technical issues around implementing Nashorn should check out the blog. Laskey said they are quite open to guest posts from developers who have been using the technology.