It’s pronounced ‘naz-horn’
submitted to the OpenJDK. In a
message to the OpenJDK announcements mailing list, Nashorn
Project Lead, Jim Laskey and OpenJDK HotSpot Group Lead, John
Coomes, have formally proposed the creation of the project.
Nashorn has been developed internally by Oracle for some time, with solid details only emerging at this year’s JavaOne. At that time, the team reported 99.99% compliance with ECMA test262, considerably higher than Rhino, which has 95.90% compliance.
It seems that the elusive 0.01% has been overcome, however, with the writers announcing a 100% compliance rate, “the current status of this project is that further work needs to be done on performance and hardening before it can be considered ready for general use.”
Voting is open to existing OpenJDK members until December 6 - although it seems unlikely that such a high-profile project would be turned away.