New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine (original) (raw)
Simone Bordet simone.bordet at gmail.com
Thu Jun 7 10:44:55 UTC 2018
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
On Thu, Jun 7, 2018 at 12:35 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
There are several replies from people that are using Nashorn but one thing that is not clear from any of the mails so far is whether these usages are via the javax.script API or by code making direct usage of Nashorn APIs.
I use JSObject and ScriptObjectMirror from jdk.nashorn.api.scripting.
I will be willing to change those usages to the GraalJS equivalents if it's going to be a long term solution (which I thought Nashorn was).
-- Simone Bordet
Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]