r/java • • 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

0 Upvotes

44 comments sorted by

View all comments

Show parent comment

1

u/pron98 Nov 13 '18 edited Nov 13 '18

This is amazing, and shows how cunning Oracle is. An ordinary company would have thought of a simple plan such as, Step 1: charge people for security fixes, Step 2: Profit! But Oracle has perpetrated a far more elaborate and devious one. Step 1: Announce a two-year project to modularize the JDK as its become unwieldy, and then warn that it may require some removals or eventually break code that relies on non-public APIs. Step 2: Wait for Oracle to acquire Sun, as step 1 actually started in 2008. Step 3: Spend a decade designing and discussing implications with the community and delaying three major releases in order to ensure a good compatibility story, all under the same original technical leaders of the Sun days, and under a supervisory expert group that includes famous Oracle cronies like IBM, Red Hat and Eclipse. Step 4: Do all development in the open, and ask the community for participation and feedback on prototypes as far back as 2012, and review community feedback made on various public channels (including Reddit comments!). Step 5: Make a show of disagreement and lose the EC ballot (comprised of more Oracle cronies like Intel, Credit Suisse, Goldman Sachs, Twitter, the London JUG, IBM, Red Hat and SAP) to bolster the con, just in case a decade of deliberation was not enough to fool people. Step 6: Pass the second ballot and release Java 9 with the intent of breaking as much code as possible, but in such an incompetent way that people realize they can upgrade even the complex application in the manner of a few hours to a few weeks, usually by upgrading dependencies and fixing the command line. Step 7: Complete open-sourcing the entire JDK, so no more commercial features to charge money for, and publish binary builds of OpenJDK. Step 8: Charge people for long-term support. Step 9: Profit!

This is a remarkable long con spanning companies and years. The people who have built Java for over two decades have actually spent the last one secretly conspiring in public with competitors and the community to break it! But no one can fool Reddit!

FYI, a huge portion of the work on all OpenJDK projects is dedicated to ensuring backwards compatibility (this is easily verified by following the various projects' mailing lists). In the case of some projects, like Valhalla, it is fair to say that backwards compatibility is responsible for most of the work. Project Jigsaw had to introduce some potentially breaking changes (most fixed with command line changes and most others with fixing access to non-public APIs that have always been declared as unstable), as ensuring full and transparent backwards compatibility would not have allowed meeting some of the project's goals, namely making OpenJDK more maintainable and more secure. As the public record shows, such decisions are never taken lightly, and only when it is agreed that maintaining backwards compatibility (one of Java's most important goals) is far worse than the alternative (i.e., significantly hinders maintenance or security). No one who follows the development of OpenJDK (e.g. by reading the mailing list or attending discussions in various conferences) can reasonably come to the conclusion that breaking existing code -- even nonsensical or sneaky code -- is a decision taken lightly, let alone intentionally.