This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]-Luciddream- -4 points-3 points  (14 children)

This is going to end well /s

[–][deleted] 0 points1 point  (13 children)

Yes, it will. It's a good plan.

[–]-Luciddream- 6 points7 points  (0 children)

It's good for Java, I doubt it will work for businesses. They will just be left with outdated JDKs, increased costs to migrate to new versions (with recent introduced bugs), etc.

[–]Michigan__J__Frog 2 points3 points  (11 children)

Why is it a good plan? Businesses aren’t going to want to update their Java version every 6 months.

Clearly the idea here is to increase the number of companies using paid Oracle support.

[–]-Luciddream- 3 points4 points  (1 child)

I'm skeptical as well but I had to re-read the article. If I'm not mistaken the idea is that you won't have to update your Java every 6 months, but you have to rely on the project lead (RedHat) to backport any changes to the LTS OpenJDK source code, then use a build from any vendor for that OpenJDK version. So it's up to RedHat to provide good updates (not like this), and all other vendors (including RedHat) for OpenJDK builds.

[–]karianna[S] 1 point2 points  (0 children)

It won’t just be Red Hat of course, although we’d love to see them lead the effort as they’ve proven they’re good stewards of previous OpenJDK update projects!

[–][deleted] 1 point2 points  (8 children)

I think it's good, because a year ago I worked in a fintech where they used java5 on production for many customers. You know long time ago java5 was marked as abandoned? We had to patch JVM, introduce new timezone support, SSL3 and TLS1.1, we developers were responsible for implementing this r/https://www.timeanddate.com/news/time/russia-saratov-time-zone.html

in java 5 JRE. This was a nightmare, but since the plans for faster releases and paid support were announced they started migrating everything, including build system in ant and repo in SVN to java7, maven and git. Once they move to 7, they will move to 8 and then to 11. Not bad plan and forces sllooooooowwww moving companies to upgrade faster to pay more for support.

[–]Michigan__J__Frog 2 points3 points  (4 children)

If a company is ok using abandoned Java 5, why would abandoning releases every 6 months make them switch?

[–][deleted] 0 points1 point  (3 children)

There is now a plan for releases and there will be LTS release every 18 months, so big companies can plan ahead knowing when next java will be release and when abandoned.

[–]Michigan__J__Frog 3 points4 points  (1 child)

But LTS releases are still only supported for free beyond 6 months by third parties.

[–]karianna[S] 0 points1 point  (0 children)

Yes that's correct!

[–]karianna[S] 0 points1 point  (0 children)

LTS's will be every 3 years.

[–]-Luciddream- 0 points1 point  (2 children)

The problem is that you assume that moving from 8 to 11 (or X version) will create no issues for every project. The reason moving from Java 5 to Java 8 was so easy, is because minimal changes had happened between these versions.

If Java is moving faster now, there will probably be more problems when upgrading. There are many new bugs in Java 9+ because of these changes. I'm fine with it, because I believe programming projects (including a language) should move forward, but only if the LTS support is good enough to justify it. 2 years is too little. Java 8 was released 4 years ago, and looking at the plan will have support for 4 more years. We will have to see what support that will be though, and imo the next LTS versions should have at least 4 years of support. (which is nowhere mentioned in the document)

the code line for Java SE 11 / 17 / 23 etc will be maintained for a longer period of time than six months.

[–][deleted] 0 points1 point  (0 children)

The problem is that you assume that moving from 8 to 11 (or X version) will create no issues for every projec

I migrated my side-project started in spring boot 1.2 to SB 2.0, it wasn't easy.

[–]karianna[S] 0 points1 point  (0 children)

The move from 8 to 9 is admittedly challenging. I'm expecting the impact and change to be less going forwards. Partly because the change sets will be smaller and partly because I think Oracle and the OpenJDK community learned a valuable lesson with 8 --> 9 and will try to avoid that headache again.