3 ms·
The modules system is not a blocker for migration at all. At this point, it is completely optional to enable it. What indeed caused breakage was the encapsulat
by samus 4y ago
The modules system is not a blocker for migration at all. At this point, it is completely optional to enable it.
What indeed caused breakage was the encapsulation effort that blocks unrestricted access to JVM internals, and that one was not even fully and forcibly turned on until Java 17.
- thriftwy 4y agoWell it requires users of your code to put a half dozen extra JVM args just to get your code (such as Java-based database like Apache Ignite) to run. You can see how such features are not super popular to the extent of widespread non-adoption of Java 11 even 10 years after its release.
- samus 4y agoOracle offers extended support for JDK 8 until the end 2030, which is more than four years longer than for JDK 11. I'd say this is the more likely reason that Java 11 is not adopted more. Spending a few hours to fire up an application to figure out the right --add-opens call really does not seem like such a big imposition to me.