Earlier quoted context omitted.
The USA and I've been doing it for two decades, honestly copyrights and licenses are not important to me. I have taken a fuck all attitude without consequence and will continue to do so forever.
Though it "sounds bad", this is a wonderfully practical approach. Why waste a lot of time with this BS?
Oracle’s Java 11 trap
221–230 of 244 posts
Re: Oracle’s Java 11 trap
#222Re: Oracle’s Java 11 trap
#223interestingly, openjdk is the top link on google for me for "java 11" search. did google do that?
Re: Oracle’s Java 11 trap
#224Java 11? At work we haven't even started to look at the migration from Java 8...
The hell? You should just be able to take your code and compile and run it on Java 8. There aren't any major comparability breaks. Just try switching JVMs and run all your unit/integration tests (you do have tests right?) Java 9 is the one that breaks nearly everything. We attempted Java 9 at our last shop and almost every dependency we used had some exception from a removed deprecated function down there in the stac…
Re: Oracle’s Java 11 trap
#225Earlier quoted context omitted.
OpenJDK is the reference implementation now so if you did find a functional difference, Oracle is in error.
I honestly don't know why anyone would keep using Oracle's version of the JDK over the OpenJDK, other than them just being used to it.
Re: Oracle’s Java 11 trap
#226Earlier quoted context omitted.
The situation is confusing but not that confusing. Java 8 has commercial features that are locked by default. You can unlock them by passing a command line flag that looks like -XX:+UnlockCommercialFeatures, so pretty hard to miss. If you use those in production, you're meant to pay. But virtually nobody does use them. In fact Oracle open sourced them all for Java 11, perhaps because of that fact. Now in Java 11 ther…
The difference is that OpenJDK N will stop receiving security fixes the moment OpenJDK (N+1) is released. LTS releases are only LTS for Oracle JDK. So no, OpenJDK by itself is not suitable for production use. To put a Java app in production securely you now need to either pay Oracle or find someone to provide security fixes to OpenJDK beyond what Oracle provides for free.
Just upgrade to OpenJDK_v(N+1) whenever it's out. Get rid of Karaf, Liferay or whatever is holding you back. Don't become a legacy app developer.
Re: Oracle’s Java 11 trap
#227Earlier quoted context omitted.
We just made it TO Java 8.
Java 8 is EOL in January for public support/security patches. Java 7 was EOL in 2015. What have you been doing for 3 years? I could guess, because I've been at companies doing the same. Active development and support on the product, but no time for tech debt. Java 9 and up I understand people getting frustrated with a more frequent LTS release and these weird microreleases every year.
Re: Oracle’s Java 11 trap
#228Re: Oracle’s Java 11 trap
#229Earlier quoted context omitted.
'Zulu', right? What's their angle?
They originally built it for Microsoft to run Java apps on Azure: https://www.azul.com/successstories/microsoft/ I guess they later figured it could be more generally useful and they could sell support for it.
From the article: They wanted to offer Java on the Microsoft Azure Cloud, unencumbered by complex licensing or end-user restrictions.
What are Oracle doing that their shiny enterprise offerings just have too much baggage attached even for Microsoft?
Re: Oracle’s Java 11 trap
#230This is not new, and as per: https://www.oracle.com/technetwork/java/javase/terms/license... it was put in place in 2017 already. Seeing that the "LICENSE" of Java 8 simply points to their website, it means that they effectively changed it for Java 8 as well. So that means that even if you're running Java, you have three options: (1) Continue using it illegally, it will probably be a low risk. This is not advisable e…
The situation is confusing but not that confusing. Java 8 has commercial features that are locked by default. You can unlock them by passing a command line flag that looks like -XX:+UnlockCommercialFeatures, so pretty hard to miss. If you use those in production, you're meant to pay. But virtually nobody does use them. In fact Oracle open sourced them all for Java 11, perhaps because of that fact. Now in Java 11 ther…
THE LICENSE SET FORTH IN THIS SECTION 2 DOES NOT EXTEND TO THE COMMERCIAL FEATURES. YOUR RIGHTS AND OBLIGATIONS RELATED TO THE COMMERCIAL FEATURES ARE AS SET FORTH IN THE SUPPLEMENTAL TERMS ALONG WITH ADDITIONAL LICENSES FOR DEVELOPERS AND PUBLISHERS.