Just noticed Java 10 (yes 10) got released! What is Oracle up to? Its a bit late for an april fools…
It’s going to get worse from here. Java 10 support ends in September. 
Don’t upgrade yet, since Ignition doesn’t run on Java 10 right now.
I read some articles and it sounds like Java is adopting a nicer release strategy with LTS releases, etc. (nice) but also completely throwing out the current versioning scheme (ugh). Stinks for you guys! Good luck.
See here for the roadmap. http://www.oracle.com/technetwork/java/eol-135779.html
So it appears that Java 9 and 10 are short term releases. With support for Java 9 ending in a few weeks, and Java 10 only supported until September.
Java 11 should appear in September, and this should be a long-term support release (5 years).
So I guess it’s safest for us to only use version 8 for now, and start using version 11 for new projects when that comes out in September.
2 Likes
The gotcha here is that upgrades to LTS versions are going to require a support contract with Oracle. Here’s a good summary from www.azul.com/java-stable-secure-free-choose-two-three/:
The implication of this change is that Java is still stable, secure and free but you must now choose two of those three qualities. When deploying Java in the future, you can’t have all three at the same time.
Let me explain this a bit more.
Suppose you are most concerned about security (as you should be) but don’t want to spend any money. To do this, you will need to switch to new versions of the JDK as soon as they are released. With no overlap (either for Feature or LTS releases) you must do this to be able to install all security-related fixes. Unfortunately, with no overlap, you must switch to a JDK release that has not had time to be tested in real production environments, so you lose the stability you had.
Alternatively, you may favour stability and zero cost. Again, this is possible; all you do is continue to use the previous LTS version after a new one is released. You continue to have the stability you’re used to, need pay nothing, but will not get security patches, as they will no longer be available for that release.
Finally, if you want stability and security, it is not going to be free. You can continue to use the previous LTS release, but access to patches will only be available through a commercial support contract.
So you either upgrade every 6 months to untested versions, use an LTS version with no updates, or buy a support contract.
1 Like
Ew. Oracle is finally moving to kill the Java platform. This is disheartening.
2 Likes
That’s not really how I see what’s happening. They’re moving to make money, but in the process of doing so, they’ve liberated all the parts of Java The Platform that matter.
There’s no longer any difference between OpenJDK and Oracle JDK. JavaFX has been separated and open sourced. Java EE has been separated and open sourced.
Companies that need a commercially-supported and constantly up-to-date JDK can use Oracle or Azul. I think there will also be some community supported LTS versions from the AdoptOpenJDK project: https://adoptopenjdk.net
We’ve (IA) been watching this all as it develops and will have some kind of statement about our support strategy in the near future.
4 Likes
Is it time time to move away from JAVA to single threaded platforms like NodeJS and javascript/typescript and alike for real time applications (as well as enterprise applications)?
Let’s not derail this thread, but, Javascript is a horrible language, NodeJS is a terrible platform, and the entire JS ecosystem is an immature shit show.
9 Likes
In view of the strong, serious and objectionable remarks on the JS ecosystem , and not to derail this thread, a new thread “J2EE v/s NodeJS for real time applications” is started.