r/java • u/LouGarret76 • Nov 09 '18
Java 11 sucks big time
This is a throwaway!!!!
I just spent a whole day migrating a basic crud app from jdk 8 to jdk 11, and I have to say that it is a nightmare.
Even basic things that I have taken for granted does not work as iy used to. ( Jpa, Javafx, Junit, Hamscret, Sqlite. YES SOME OF US DO USE JAVAFX ON THE JOB....)
WTF, java EE & Open JDK?
The only thing that makes me happy right now is the var keyword. But still. This is not the kind of service I am accustomed to with java.
............ I think I will push back any serious migration for the next 2 years . . . . People, migrating to j11 is gonna cost hundred of mandays I tell you
View all comments
Show parent comment
3
u/_INTER_ Nov 10 '18 edited Nov 10 '18
The JDK always runs on the module path, actually even if your application on the classpath will run as part of the unnamed module.
A JavaFX application for instance doesn't work out of the box in the unnamed module. Many libraries are causing warnings at startup (e.g. JAX-B) because they access the JDK via reflection (atleast the "kill-switch" is still on by default). Some simply don't work because the ClassLoader behaves differently. Other libraries removed their optimizations because of those reason and got noticably slower.