News for hackers. Stuff that matters.
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by pradn on Wednesday June 06, 2018 @03:50PM (#17250468)
Has anyone used Nashorn? For what use-cases did it make sense to run JS inside of a JVM process?
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by adrianpike on Wednesday June 06, 2018 @03:58PM (#17250533)
JS in the JVM is used heavily in Mirth (https://www.nextgen.com/products-and-services/integration-en...) for scripting of channels and data transformations. It's kinda janky but runs a lot of healthcare systems. It's using Rhino, not Nashorn, FWIW.
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by lmm on Wednesday June 06, 2018 @04:48PM (#17250977)
User-defined scripting of a system written in Java. Everyone knows Javascript and it's easier to allow a user to submit text scripts and run them via the embedded engine than require users to run some kind of plugin build process.
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by Roboprog on Wednesday June 06, 2018 @05:43PM (#17251353)
We are. We use a library called rules.js to do some basic content validations that can run on either/both the client and server.

And now I look foolish for suggesting it (using Nashorn).

Re:JEP 335: Deprecate the Nashorn JavaScript Engine by kenan_warren on Wednesday June 06, 2018 @04:00PM (#17250556)
I know of one CMS that uses it extensively underneath to construct the pages.
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by MrBuddyCasino on Wednesday June 06, 2018 @04:59PM (#17251067)
Yeah Alfresco. Was a stupid idea, second only to their decision to roll their own crappy UI framework.
Re:JEP 335: Deprecate the Nashorn JavaScript Engine by Fishkins on Wednesday June 06, 2018 @07:09PM (#17251915)
I use it for server-rendering React in a Spring app