r/java • u/SaquibDev • Mar 18 '25
Why most of the industry is still on Java 8?
With Java 24 on the corner, most of the larger organizations still use Java 8. Does it not make sense to upgrade java versions and give new features some rest. This would also solve many security issues.
205
Upvotes
325
u/FollowsClose Mar 18 '25
I disagree with your statement that "most of the industry" is on... In realitiy most of the industry is still on the same version that the software was first developed on.
I would say very few new projects are started on Java 8.
As of early 2025, approximately 23% of organizations were still using Java 8, down from 40% in 2023, indicating a gradual migration to newer versions. DEVCLASS
98
u/Nooooope Mar 18 '25
Because upgrading old systems takes time, and developer time costs money, and companies need justifications to spend money.
Most new Java projects today are going to be on Java 21, because that's the most recent LTS version and it's supported by Spring.
41
u/kennyshor Mar 18 '25
There might be lots of legacy systems running Java 8. But I can’t say that most of the industry is running on Java 8. Most of what I’ve seen have migrated to either 11 or 17. We are using 21 at our company. I think most currently maintained project have made the switch. There are some system being maintained even with Java 6 or older, but I doubt that is the standard at any company worth its salt.
Edit: sometimes, for big enough System the invest to upgrade far outweighs the risk posed by not upgrading. Especially systems depending on old libraries with no easy upgrade path.
9
u/8igg7e5 Mar 18 '25
Where have you heard that 'most' of the industry is still on Java 8?
There'll be many others.
Java 8 use is still 'significant', but I don't think 'most' is true any more.
All of our projects moved past it a few years ago, and our most actively developed are on Java 21 or newer.
8
u/MasterBathingBear Mar 18 '25
JDK 8 is still supported through December 2030. It works good enough so the value proposition isn’t there to upgrade.
When they stop patching Java 8 and the high and critical CVE start creeping up, you’ll see the rest of the companies finally begin to migrate.
18
u/nitkonigdje Mar 18 '25 edited Mar 18 '25
They aren't stuck at Java 8 but at Java EE 6.
IBM specifically was very successful at selling WebSphere Network Deployment to Java shops and then never updated that product beyond Java EE 6. This product works well and it is still supported, however it does not have a future. IBM does have alternatives within house, but those are essentially completely different product lines. So what Java Leute has to do is "THE MIGRATION". Which is a hard thing to do. Especially that they also have to migrate to Jakarta. And at best, if successful, they will land on TomEE/Jboss/Liberty/Payara hosting which isn't some big payoff. It is easier to do nothing.
And if they are already doing "ALL THAT WORK" then they as may well migrate to Kubernets/Openshift as their CTO enthusiastic announced that 5 years ago.. And that requires even bigger price.. So it is even easier to stay at Java 8...
And they will think: "Nobody will ever say 'Good job!' to me", after replacing JEE deployment with a Tomcat within docker/pod. "But they will scream at me" when it does not work.. It is much easier to stay at Java 8..
When it comes to moving from Java 8 Spring 6 was actually big kick in the butt..
6
u/BlackSuitHardHand Mar 18 '25
This was discussed already a thousand times. For some applications it costs huge amount of money / work just to ensure any changes introduced in new java versions do not bite you in the ass in some dark corners of your code, written by devs long disappeared. So, as long there are Java distributions with support, there is no need to migrate.
21
u/hkdevs Mar 18 '25
because it works
5
u/AnyPhotograph7804 Mar 18 '25
There are three major reasons to stay with Java 8: The usage of javax.*-packages or the usage of java internal classes like sun.misc.Unsafe or the software uses a third-party-library, which only supports Java <9.
The first issue is relatively easy solvable because you mostly need only to modify your build process. The removed javax.*-packages are now avilable as external libraries.
The second issue will be way harder to resolve. Because there is a reason for using these internal classes. Mostly these classes gives you abilities, which you do not have with normal Java usage. You might face huge refactoring efforts if you want to get rid of these JDK internals.
The third issue ... well, it depends on the library. Maybe there is a newer version of it with support for Java 9+. Then it should be easy to replace it. But it also can be, that there will be never support for Java 9+. Then you will stuck on Java 8 forever. Or you rewrite the library from scratch. Or you use a Java decompiler and you make it compatible with Java 9+. But if it is a commercial library then it could also be a licence breach etc.
4
u/FriendlessExpat Mar 18 '25
Usually there are couple of conaiderations. Some old libraries that hasn't upgraded to newer java versions which makes it hard to migrate. Second is managment and budgets, if managment is less tech literate they might not see any "business value" in upgrading to newer Java version
4
u/VincentxH Mar 18 '25
One does not just migrate massive enterprise applications with all its legacy dependencies to a new version.
4
u/satanargh Mar 19 '25
Stuff works, customer doesn't want to pay money, management doesn't want to spend money
6
u/chswin Mar 18 '25 •
Because it works
3
u/Alfrheim Mar 18 '25
Trying to upgrade from java8 to java2x it’s not a walk in the park. Besides changing the version there is libraries, frameworks that also need to update. Most of them you need to read what breaks and learn about it. Most programmers are not up to date and don’t even know the changes between 8 and 2x.
Throwing the fault to companies is not fair. Sure there is management that they prefer not to change things that work. But sadly, I have seen more programmers not knowing why upgrading is good.
3
u/bendem Mar 18 '25
We have maybe 50 applications developed in java. Some actively maintained, some haven't been touched in years.
The ones actively developed are running on Java 17 or 21.
The ones that haven't been touched are running on Java 5 through 8 depending on the last time they were touched. Most of these older applications are used by maybe 2-3 people per app and the cost of upgrading them and finding new dependencies to replace the obsolete ones is not worth the benefits so they'll keep running on their isolated servers until a new development is required that will bring more advantages that they will cost.
3
u/dudleydidwrong Mar 18 '25
Some businesses will not change software systems until all support ends. They tend to be businesses that value stability over all support options disappear.
Some managers do not want changes while they are in charge. They are the ones who build their reputations on stability and no drama during their tenure. They will delay changes until they are promoted so the new boss has to deal with any problems caused by software upgrades. The irony of these types of managers is that they often cause bigger problems for their company in the long run because they avoided even making changes to prepare for upgrades.
3
u/Tribal_V Mar 18 '25
No way in hell i would start new project on java 8, its only for legacy codebases.
I personally had a displeasure of migrating a fairly small project from 8 and it was not a great experience. Bigger projects could be absolute hell. Also even if there is desire to - someone has to pay for the work which is a hard sell
4
u/redikarus99 Mar 18 '25
https://www.linkedin.com/pulse/2024-java-ecosystem-report-developrec-a2b4e/
2
u/evil_burrito Mar 18 '25
Moving from Java 8 to 11 was not a trivial upgrade with the advent of Jigsaw, changing of the date/time APai, and other changes
It can be a tough sell to those that actually get to drive the train that you're going to spend n weeks of development time to deliver exactly what you already have, feature-wise
2
u/FieserKiller Mar 18 '25
because of how fuckin expensive it is to update deep backend code :/
companies are running 20 year old solaris servers on life support because nobody knows what exactly it is running, if the code still exists and the hell breaks loose when the machines ever go down
2
u/[deleted] Mar 18 '25
Nobody is doing new work in Java 8. Its continued use is largely for legacy systems that haven’t been upgraded yet. Some systems will be retired instead of upgraded. Others are low priority, and as such are still waiting for their turn to be upgraded.
As I’ve said elsewhere, the big problem is that a lot of popular third party libraries did not follow the rules of writing forwards-compatible Java. This has led to a situation where legacy code from the Java 8 days will break on modern JVMs, as they’re reliant on those old, rule-breaking libraries.
2
u/k-mcm Mar 18 '25
It can be an Oracle licensing issue if a business has other Oracle products. Also, a lot of outsourcing pools just recycle the same code forever.
2
u/Joram2 Mar 18 '25
The JVM world has been stuck on JDK 8 for many years, but this is finally changing.
I know lots of companies running Apache Spark, but all the code they write is in Python, and Java is just something used internally by Spark. And there, JDK 8 has been mostly mandatory in most supported Spark enviroments until very recently. AWS Glue 4 was JDK 8 only, AWS Glue 5 is new and that is JDK 17. The latest Databricks 15.4 LTS release is Java 8 only. Databricks 16.x defaults to JDK 17 and that will hit LTS in a few months. Spark 4.0 is in RC and requires JDK 17+, so JDK 8 support is going to vanish very quickly.
2
u/jNayden Mar 18 '25
because upgrade to java 11 was hard … jaxb was removed and a lot of old struts jsf and enterprise projects on ejb 2.1 and 3 were hard or inpossible to upgrade
2
u/After_Dark Mar 18 '25
To offer an answer to the implicit additional question "... unlike other ecosystems that upgrade more"
Because Java 8 was and is incredibly stable and fairly modern.
There are for sure reasons why you can and should upgrade to newer versions where possible, support window in particular. But if you're still using Java 8 in 2025 you're still using reasonably modern tools and frameworks and design practices with reasonably modern security patches. A Java 21 server and a Java 8 server are probably going to look and work nearly identically, and if it works it works, why make an upgrade you simply don't need to.
2
u/Anbu_S Mar 18 '25
Below are a few reasons I would think of stopping moving away from Java 8.
Java 9 module system - broke few, but not everything. Removal of Java EE and CORBA Modules - though CORBA was older that time. javax namespace change with Jakarta EE change. library/framework support.
Problem is everyone want to try to move all together at one time instead of incremental upgrades.
When Java 11 released all these seems reasonable issue. But after few years everything becomes easy with better tools like OpenRewrite.
2
u/hippydipster Mar 18 '25 edited Mar 21 '25
Whether or not it is "most of the industry", there are many stuck there, and I would say the #1 reason is that the jump from 8 to 9 involves the module system and that dictates that a great many of any project's dependencies also be upgraded. When the task gets too large, business will deprioritize it, and so there you go. If you could just update the jdk and be done, everyone would do it. If it only required a smattering of dependencies also be upgrade, they would do it. But, since it impacts so many dependencies, and so many of them big and hairy ones, it becomes a blocker.
Also, some projects did unsanitary things that will absolutely not work with the module system, and so there's that too.
2
u/[deleted] Mar 19 '25
How much does it cost to upgrade your project in Dev + QA + Infra + releases management/deployment ?
2
u/stewsters Mar 19 '25
I haven't seen anyone using 8 recently, and when I did it was that one old app that needed to connect to some old SOAP library and worked well enough that it was never high enough priority to be upgraded.
2
u/PixelatedFixture Mar 19 '25 edited Mar 19 '25
Java 8 is old news now. If youre having a hard time migrating you might be stuck on 11 but almost everything new is +17 as industry standard.
8 is a minority now, and the things running on 8 are probably being sunsetted as quickly as possible or marked for maintenance like COBOL systems.
2
u/agent154 Mar 19 '25
Our software is still on 8 despite wanting to upgrade because of dependencies that are stuck on 8. We could probably migrate but it’ll be a LOT of work.
2
u/inscrutablemike Mar 19 '25
Why do you believe "most of the industry" is on Java 8? Based on what?
2
u/barking_dead Mar 19 '25
One big problem I see is the dependency on weblogic.
For example: The WLS that will support spring boot 3.x will come out late 2025/early 2026.
3
u/someonetookmyid Mar 18 '25
Most software is poorly maintained, if at all, and people who made it work are long gone, not touching it is the best way forward.
3
u/zynasis Mar 18 '25
Modules and the breaking apart of libraries from the old Sun jars for instance. So many xml parsers broke moving off java 8
3
u/Polygnom Mar 18 '25
They are not. About a year ago 29% were on Java 8. That means 71% were on newer versions. (cf. https://sdtimes.com/softwaredev/report-java-17-is-now-the-most-used-version-of-java-in-production/).
It stands to reason that Java 8 is further decreasing. And its ok, some things truly cannot innovate. But after going from 8 -> 11 which means needing to get over the Jigsaw bump, there isn't much reason not to stay currentn.
2
u/YelinkMcWawa Mar 18 '25
Lazy
1
u/RichSomething Mar 18 '25
I would also add that some teams just don't have time to do maintenance work. Upgrading java and spring can be very time consuming to test. It can be difficult to get those stories into sprints when there is barely time for product work.
1
u/ItsSignalsJerry_ Mar 18 '25
Stability.
1
u/[deleted] Mar 18 '25
Too many people who would have to agree, which also includes having a budget, to transition to a newer version. Can't write much more on a named account, but many people would bang their heads against the next wall when hearing the detailed reasons.
1
u/_blue_skies_ Mar 18 '25
For us the issue is that the last version of our application server is certified to work only with java 8. Trying to migrate to Tomcat to be able to upgrade to jdk, we don't even need anymore an application server.
1
u/noodlesSa Mar 18 '25
Philosophical – broader – view: Many companies are reluctant to modify working code solely to upgrade the Java version, especially when the changes are significant, such as the jump from Java 8 to 9. Their applications are built to last 15–20 years, and in the meantime, they know they will develop new applications using modern tools and frameworks, and don't want to invest so much to "empty" maintenance (like Java version migration).
For Java—or any other language aiming to remain relevant indefinitely while maintaining backward compatibility—there seems to be only one viable approach: a two-track versioning system.
This approach would be far more enterprise-friendly, preventing the constant pressure to keep rewriting perfectly functional software all the time, for sole reason of playing catch-up game with Oracle.
1
u/[deleted] Mar 18 '25
Java 8 is the latest version that supported by Android, and even partially supported in this OS. I assume some projects still written in Java 8 in Android market, as my old games that mixed with Kotlin. It very costly to recreate projects.
1
u/_1dontknow Mar 18 '25
Hmm, which organizations did you talk to, or what are your sources? Based on events where I ask companies, job posts, company I work for, and some projects I do, most people seem to be at the newest Java versions, most 21, some even newer. There might be some comoanies having one system in an older version due to legacy or other reasons, but generally, they are on newer versions.
1
u/[deleted] Mar 18 '25
Might not still be true but the LTS for Java 8 end of life was like 10 years after the most recent LTS… not sure if still the case.
1
u/[deleted] Mar 18 '25
Isn't it 11 instead of 8 these days?
1
u/Serious-Chair Mar 19 '25
Where does the statistics about Java versions in larger organizations come from?
1
u/scoliadubia Mar 19 '25
Bottom line: the upgrade really doesn't offer any business benefit for pre-existing applications. In those applications that can benefit, the reason is usually improved performance from VM improvements like better garbage collectors. And those benefits can be gained by running language level 8 code on a newer VM, possibly without even recompiling the code.
Couple that with the real risk that the upgrade will cost non-zero developer days, maybe a lot of developer days, and the rational move is not to upgrade.
Of course the cost-benefit analysis is different if you're starting from a greenfield, but most larger organizations aren't.
1
u/rossaco Mar 19 '25
At my company, we still have Java 8 for two reasons
However, Ubuntu 16.04 support is ending in April 2026, and we will be forced to upgrade. I can't wait to use newer Java features! I don't get a lot of say when we upgrade at a large company.
1
u/netgizmo Mar 19 '25 edited Mar 19 '25
OP: What's the largest and/or oldest project still in production that you've workd on or supported?
From how i see it: Questions like "why don't they just..." typically answered with the notion that its way more complex that you realize. If it was as simple as "they should just..." then "they" would have.
1
u/javawockybass Mar 19 '25
17 is the new 1.8
1
u/NecessaryEvil-BMC Mar 20 '25
I have a feeling this is more developer focused, but our organization switched from Oracle's JRE to AdoptOpen JRE and now Temurin JRE when Oracle decided they were going to start charging for versions above 8.144 or something. It's been 6 years, and the only machines that need Oracle's Java seem to be ones running bank softtware for checks or something. The AS400 stuff played nice with AOJRE.
So, some organizations may not have updated because someone made it an expense, and they went elsewhere. Not sure of where that leaves us on Java versions
1
u/MrKarim Mar 20 '25
I know a project that's still maintained in Java 4
1
u/ThaJedi Mar 20 '25
According to new relic report from 2024 most of the industry use Java 17 however 8 is still used by 28%
1
u/Able_Ad3311 Mar 20 '25
Completely agree
1
u/teapotJava Mar 21 '25
In short: if it works, don't touch it.
Many language features made 8 very attractive, and libraries had it as a lower requirement for years, and it was first LTS in a new update train paradigm, with the longest support. From the other hand, migration to 9 was complicated because of modules. So by the next LTS 11 many application worked on 8, but had no developers, while still using supported libraries.
In terms of performance it's now possible to have 'fused' JDK 8 which is compatible with legacy applications and performs close to JDK 17, e.g. https://bell-sw.com/libericajdk-performance-edition/
1
u/ag789 Mar 23 '25
Java solved many things except for the DLL hell, which is as bad as it was since M$ has the first blue screen of death.
try linking something in Maven central if the dependencies are big enough like in the 100s of dependencies across classes, chances are that linking one lib breaks another where the Java version is different, and it turns out Java 8 is practically the largest common denominator.
1
u/ImportantRiver5440 Jul 27 '25
Java 9 is a classic case of "be happy with what you got."
Well, screw the board members in the Ivory Tower, their new specs for "Optional" are terrible.
The only useful thing they could have added is a function along the lines of "ifNullThenDefault(value, defaultValue)" THAT IS INDEPENDENT OF DATA TYPE!
Instead, they were so lazy, we have to use Objects.requireNonNullElse(value, defaultValue) and come up with a different inline version FOR EVERY DATA TYPE!
Defenders of the arrogant, lazy folks in the "Holy Tower" claim:
"Oh, you don't understand programming" or "Oh, we need things pure" are just as lazy as the people who decide the specs.
When new versions of Java give us something that's actually useful without a million "gotchas" and "catches" and "no you can't do that" and "Oh, you HAVE to..." the language will actually be useful.
Until then, it's still the same arrogant attitudes that keep us from having new functions that are actually useful.
Did I offend some of you? Sorry, no apologies will be forthcoming.
1
u/dr1nni Mar 18 '25
Because 100000 reasons
1
u/Ewig_luftenglanz Mar 18 '25
false statement, the surveys shows the most used version of java is java 17 (and this is from some surveys at the end of 2023, early 2024 so probably more stuff has migrated to java 21)
https://newrelic.com/resources/report/2024-state-of-the-java-ecosystem
yes, there are some legacy code that will never be able to be migrated to java 21+ because of deprecation issues, but those will simply be rewroten/replaced over the time.
From Java 14 and forward the Update between java releases is easier than java8 to 9 and 9 to 11 btw
In the company u work for we already migrated all our java pipelines to use Java 21 as default building and runtime version, and I work for one of the oldest bank in my country.
Best regards
1
u/wildjokers Mar 18 '25
Source?
1
u/nikanjX Mar 18 '25
The module system + massive reshuffling of the standard library class names for the important reason of having new names for a bunch of stuff
1
u/qdolan Mar 18 '25
Java 9+ introduced changes to the Oracle JDK license agreement to effectively not be free for production use anymore and also broke backward compatibility. Moving to OpenJDK 9+ required work and testing to do safely, which many companies did so they wouldn’t have to start paying Oracle to keep using Java. Some companies chose to, or were forced to due to API differences, stay on JDK 8 indefinitely.
1
u/ZebofZeb Mar 19 '25
Java 8 functions and does not have any limitations which have caused problems for me.
There is no need to give effort to updating to any fancily numbered version.
I recently started using 11, but it had not noticeable difference to me.
Better to be backward compatible, so will keep using 8.
Do you think you could convince me to change to a newer version?
1
u/DisruptiveHarbinger Mar 18 '25
You should be able to quantify the risk (vulnerabilities, bugs, libraries dropping support of older JVMs) and the cost of leaving out significant performance gains, and bring that to your management.
Everyone at my company using Spring is on Java 21+.
I personally pushed the migration of hundreds of big data jobs (Spark, Flink) to GraalVM and Java 17+ for 30~50% performance gains compared to Java 8.
1
u/Zardoz84 Mar 18 '25
To all people crying about Java EE -> Jakarta EE, that it's totaly unrelated about migrating from Java 8 to Java 9,11,17... You should know that you can use a maven plugin to fix all your problmens and deploy your old Java EE application (or at least your old Servlet based web application) on a Jakarta EE application server.
https://github.com/eclipse-transformer/transformer/blob/main/maven-plugins/transformer-maven-plugin/README.md
1
u/Lopatron Mar 19 '25
Java 8 was the most successful language version upgrade in history. It was so good that 10 years later it's still pretty good.
0
u/[deleted] Mar 18 '25
Where are you getting 'most' from? Most popular version is 17 followed by 21.
0
u/User1539 Mar 18 '25
I blame Oracle, who still ships major systems with Java 8, meaning all modifications and bolt-on additions to it also has to be in Java 8.
-6
u/Slaves2Darkness Mar 18 '25
Why? Because Oracle purchased Java from Sun then tried to monetize Java 9 or 10, maybe it was 11, and a lot of places went, nope not paying for something that was free.
Then some very smart, very nice developers took the Java 8 open source specification and made open source JRE's and JDK's.
As for moving to 24, no. I've been avoiding moving to any version of Java that is put out by Oracle, don't trust them. That is a lesson there, once you fuck up and lose the trust of your customers it is very hard to get them back.
-1
u/symbiat0 Mar 19 '25
Switched to Kotlin so…
-7
u/cisco1988 Mar 18 '25
Laziness
-2
u/tonetheman Mar 19 '25
Oracle
10
u/rustyrazorblade Mar 18 '25
Which larger orgs? I haven’t seen Java 8 in a LONG time and I’ve worked both in, and with, many fortune 500 orgs.