New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine (original) (raw)
David P. Caldwell david at code.davidpcaldwell.com
Sat Jul 7 15:13:52 UTC 2018
- Previous message: how to split up runtime / development parts in OpenJDK 11?
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I use Nashorn heavily (as well as Rhino) to power a number of applications I’ve custom-built for customers.
So I’m quite concerned about the news it may be going away. Although a Nashorn that lags other JavaScript tools isn’t the ideal, it’s still significantly better than the alternatives as they are currently available.
As this is apparently the place to give this feedback, I wanted to do so. Thank you!
— David P. Caldwell http://www.davidpcaldwell.com/
- Previous message: how to split up runtime / development parts in OpenJDK 11?
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]