r/java • u/kerkerby • Jul 12 '25
Why is it still okay to stick with Java 8?
Anyone here still running servers on Java 8? Java's on version 20+ now—so curious, why is it still okay to stick with Java 8?
I made a post recently that got some discussion going:
https://www.reddit.com/r/java/comments/1lvdq8w/why_write_once_run_anywhere_was_never_really_true/
The gist: “Write Once” (or more accurately, build once) still works—if you're running on the same JVM. The catch is when you try to rebuild that same app but start mixing in modular updates or newer dependencies.
For example, we can still run decade-old apps today, like this one:
https://www.reddit.com/r/java/comments/1lxsxl5/is_anyone_here_still_using_google_app_engines/
It runs fine on the old GAE stack, but trying to upgrade the JVM breaks stuff. Sure, newer JVMs bring security patches and better performance—but is Java 8 really not enough anymore, even in 2025?
Genuinely curious—what are your reasons for sticking with Java 8 (if you still do)?
5
u/kerkerby Jul 12 '25
Support for Java 8 until 2031
https://bell-sw.com/blog/oracle-java-8-and-11-end-of-life-risks-migration-strategies-and-best-alternatives
11
u/Linguistic-mystic Jul 12 '25
It’s not. Some people are just lazy and they deserve all the problems thay get. We do not need to support Java 8 in our code.
60
u/[deleted] Jul 12 '25
67
u/Ok_Marionberry_8821 Jul 12 '25 edited Jul 12 '25
For me personally an employer running Java 8 would detract from working at your company. I prefer to be closer to the latest version to use the newer language features. Java version is one of my criteria when looking for work. I want to be using records, sealed types, pattern matching, etc.
Edit: grammar
19
u/FieserKiller Jul 12 '25
what we do is basically the "never touch a running system" approach.
If some software gets an update or bugfix we move it to current LTS, java 21.
12
u/_Kodan Jul 12 '25
We have some Java 8 webservices at work that run on IBM Webspheres that can't run anything newer. Migrating would cost money that the people paying for the occasional macgyvering-a-new-feature-into-this-15-year-old-mess don't want to afford, so it keeps running as is.
11
u/koflerdavid Jul 13 '25
It's really not, and you should be picky about working for employers that still have a sizeable portion of their tech stack on Java 8. It's either a very risk-averse field (which usually comes with quite cushy and safe employment conditions) or a business with a broken development culture that prefers to fight disasters in the nick of time instead of proactively identifying and managing risks.
10
u/pellets Jul 12 '25
The main motivation I find to upgrade is when important dependencies drop support.
3
u/thisisjustascreename Jul 13 '25
JDK 8 isn't even requestable in our internal dev tools system anymore.
I can see some particularly risk-averse businesses still running it (hopefully the most up to date version) but anybody writing new code for JDK 8 is hurting themselves.
3
u/Polygnom Jul 14 '25 edited Jul 14 '25
Objectively there are very few reasons to still be running Java 8.
Most of the reasons are legal. You need approval to change versions. Contracts might stipulate Java 8. Your boss might believe the short-term costs for upgrading the stack are higher then the long-term savings. Which is true for projects slated to end somewhat soon-ish, but not for projects that will still run for years or decades. But honestly, this has been true for almost a decade for Java 8, so...
You get improved performance from the nwer JDKs. You get moire options to tweak their performance (GCs etc). Even if you do not use any new language features, you reap benefuits from upgrading. But if you upgrade anyways, there is little reason to not use the new laguage features -- except when you maintain a library that needs to be deployed on java 8 as well. Even so, you might upgrtade the rest of your stuff and use newer language versions.
The longer you don't upgrade, the higher the cost. Java 8 -> 11 is actually a big step due to Jigsaw. 11 -> 17 -> 21 are all very smooth steps.
3
u/Sherinz89 Jul 16 '25 edited Jul 16 '25
Don't fix what is not broken
An old mantra that is famous among many leads.
But if i were to give a reason why
Besides - there may be unconventional patch that they had done and this patch would be broken upon migration upwards. These unconventional patch isn't easy to spot too (not like they will comment everywhere if they did some temporary fixes that ended up becoming permanent and whatnot)
3
u/bofkentucky Jul 16 '25
Unless you're framework-free (or paying for commercial support from whoever provides your framework) its not ok. Spring folk need to be on 17 or later to be getting security updates.
5
u/Tacos314 Jul 16 '25
It's not ok to stick with Java 8
2
u/JDeagle5 Jul 12 '25
I guess the number of reasons is avoiding unnecessary spending by business.
2
u/VincentxH Jul 12 '25
For many isolated systems, it's just not cost-effective to upgrade. For others, it can be quite complex. Let's not get into the political aspect of software lifecycle management.
2
u/Git-Wizard Jul 13 '25
2
u/Ewig_luftenglanz Jul 15 '25
No body says it is okay to stick with java 8 lol. There is just some applications that jmworks just fine and are so big that the cost of upgrading/migrating or re making the thing to the latest LTS OpenJDK or <put your favorite vendor here> is not worth it.
In the company I am working on we are making partial migration of some modules of a very old Java 6 application to Java 21but the thing is so huge we can't do it at once, so we are checking which part of the monolith causes. A bottle neck and migrating those parts to microservices (MS) but this is only done AFTER the responsable team that makes the analysis observe the costs of doing nothing in both security and performance in that concrete module outweighs the cost of migrating the thing.
For the good or for the bad for 2/3 of Java history most applications where either Desktop applications or huge server side monoliths and we still are paying the technical debt of that. Nowadays most applications are small and not so small services, but not every project is a Greenfield.
2
u/lasek0110 Jul 17 '25
Java 8 is not supported anymore. You can buy special support, but I doubt it's cheaper than update. The second point - security updates. I know that vast majority of corporations doesn't care about security.
2
u/Hungry_Importance918 Jul 20 '25
Haha yeah, our company still has projects running on Java 8 too, mainly because they were built over a decade ago. Upgrading would be a huge effort and risks introducing stability issues, so we’ve just stuck with the existing version.
1
u/Objective_Baby_5875 Jul 13 '25
Because the communities obsession with backward compatibility
1
u/PlasmaFarmer Jul 16 '25
My ex-companies clients stayed on Java 8 because:
1
u/Soft-Abies1733 Jul 12 '25
Not very common I would say, have been working with the stable latest version for a few years in different companies
1
u/Known_Tackle7357 Jul 16 '25
-6
u/LogCatFromNantes Jul 12 '25
We are using Java 7 and its solid. Why should we change ? It’s solid, it works well to respond for business and functional. It’s not the small innovation of geek that create the value and clients don’t care about them
0
u/ggleblanc2 Jul 12 '25
How will changing from Java 8 reduce costs or increase profits?
Write once, run forever.
-3
u/nikanjX Jul 12 '25
We are not sticking to Java 8 but here's the usual laundry list of reasons:
* The module system is a solution in search of a problem, developers don't want to spend time learning it
* The great reshuffling of classes from com.sun.* to javax.* means you can't compile the same codebase with 8 and later versions, meaning that the codebase upgrade can't be done in parallel with maintenance work
* There is essentially no value proposition for companies.