The second Java enhancement proposal (JEP) of 2020 has landed! Following JEP 371: Hidden Classes, now we have a second full-fledged candidate JEP with a decent shot at making it into JDK 15. That said, some voices in the community don’t agree with the proposal. Let’s take a closer look.
jjs tool. The JEP has been proposed to target JDK 15.
In JEP 372, Laskey writes:
With the rapid pace at which ECMAScript language constructs, along with APIs, are adapted and modified, we have found Nashorn challenging to maintain.
This latter comment is a sentiment mirrored by some in the community.
“We have found Nashorn challenging to maintain” pic.twitter.com/UqNqboAaGP
— Scott Selikoff (@ScottSelikoff) February 27, 2020
The aim is to remove two JDK modules:
jdk.scripting.nashorn, which contains the
jdk.nashorn.api.tree packages, and
jdk.scripting.nashorn.shell, containing the
jjs tool. Laskey further states that it is not his intention to touch the
SEE ALSO: JEP 371: Hidden Classes in Java
However, some members of the community are less than pleased by this suggestion. User BlueGoliath on reddit wrote: “Not nearly of a positive action as many think it is, IMO. If Oracle/JDK developers are going to drop features like JavaFX and Nashorn like that then people are just going to ignore otherwise centralized and dependable baked-in features for potentially worse off third-party ones. Java has historically been known for being highly backwards compatible and this hurts that perception.”
SEE ALSO: Java trends: Top 10 Frameworks in 2020
At the time of writing, there are no responses on the jdk-dev mailing list debating the merits of this proposal, so we’ll have to wait to find out what the JDK developers think.
Do you have a strong feeling one way or another? Let us know in the comments. Otherwise, why not check out the JEP in all its glory here.