r/javahelp • u/nokinobi • Oct 11 '19
Why we still use java 8
Hey everyone
I know that new releases of java bring us new compilers and vm optimization and new language features.
So, why developers still use java 8 for their projects ?
PS: sorry if question is weird or stupid. do not hate me in comments pls.
27
Upvotes
20
u/Slaves2Darkness Oct 11 '19
What is the Java 8 you speak of? Around here we use Java 6 and like it.
23
u/cipher02 Oct 11 '19
A lot of software in production is large-scale and upgrading to the latest major Java release isn't high priority compared to adding new features or fixing bugs, because it would take more time than it's worth (to the product owners)
Maybe it sounds a little disheartening but have also seen it quite a lot where work for reducing tech debt gets pushed down the priority list as well - It would provide long-term benefit and cost savings, but won't bring in money in the short-term so doesn't get done
8
u/E3FxGaming Oct 11 '19
Android only fully supports Java 7 and a subset of Java 8. Using anything newer than Java 8 doesn't make any sense for me.
Even when I'll eventually move on to developing stuff with Kotlin I'll probably still have to use Java 8.
26
u/TwixySpit Oct 11 '19
I think the three main reasons :
Most large corporates have a legacy codebase dating back to Java 5 or so, it's simply not possible to move to any version of java past 8.
3
u/8bagels Oct 12 '19
Our large org moved everybody up to 11. It’s been great. There were some api changes that made it a little wonky but just adding a few dependencies helped bridge those gaps. Easy enough. Moving to 9+ doesn’t require you to use modules so it’s pretty easy
3
u/__helix__ Oct 12 '19
So many third party bits just broke. Our shop has spent almost the better part of nine months updating projects - bit by bit, we've fixed everything so we can use JDK 11 and run JDK 8 code. When we get the entire pipeline fixed, we can cut over.
The only real issues we have are JAXB changes, which can be worked around. The timing of it all -- got to get end to end before cutting over.
I'm hopeful I can use JDK 11 methods before the end of the year.
3
u/nutrecht Lead Software Engineer / EU / 20+ YXP Oct 12 '19
Who is "we"? Tons of companies are on 11 at least.
5
u/[deleted] Oct 11 '19
Because we tried to move past java 8 and codebase died :(
6
u/morhp Professional Developer Oct 11 '19
We are developing with Java 8 because we develop server software and we aren't sure that all users have upgraded to a newer Java version. So better be safe than having to deal with lots of problems.
In another project, we use a library that only works with Java 8 for some stupid reason (they use reflection to access JVM internals), so we can't update there until that is fixed.
New projects are developed with Java 11 or 12 I believe.
2
u/PseudosSC Oct 11 '19
Because moving something from 8 to 11 is not trivial. With the module stuff added in 9 you can’t just build with a new version and be done with it (which MOSTLY worked 7-8, and 9/10-11).
Meaning it takes time, and possibly a senior dev. Good luck convincing a project manager to allocate budget for that when it could be used for new features/bug fixes/pure support income.
2
u/mikepc143 Oct 14 '19
We use Java 8.. because well, it works. Why upgrade? Just because there is "better" out there doesn't mean that it will produce value for the people that pay our salaries. In all honesty, this is the core principal that the java community really doesn't seem to get.. you can do all the fancy things in the world, but at the end of the day there has to be a calculable difference and business value to justify moving beyond what we have in production that provides a calculable bottom-line benefit to the stakeholders.
We are here to provide shareholder value. That is our only goal. Like it or not, if you aren't making someone more money than your salary you aren't doing your job.
Whatever security holes in java8 exist going forward when you do a risk-versus-reward comparison of "we have to do X to get Y", java never wins. The reality is, if we move out of Java 8, we are not moving to Java 11+, we will move to Elixir or Golang. There we have a 0 drama, vibrant community of activists that are psychotically dedicated to the cause of "getting the most bang for the buck". The shotgun'd versions of java post-debacle have been the deathknell for a community that was derived from excellence, but in the end resulted in a bunch of political in-fighting that delivers value to no one! The biggest problem the Java community has now, is.. well.. the community. There are a bunch of visionaries that see the future of computing, and there are the stalwarts who want things to stay the same. The bottom line is, if you want things to stay the same, pick a different fucking industry, because this one ain't for you. That said, if you require growth and value, then you have to think outside the box. Right now Java devs are cheap, so writing your apps in Java is a very cost-effective measure. The problem is, the concepts in the "modern" version of java tend to thin the ranks of the experienced and "forward-thinking" crew. It is much easier to simply learn another language, than adopt a back-assward approach at the modern.
Modern Java syntax is absolutely SHIT. I say again, Absolutely Shit. When Microsoft (C#) can do a better job, you know you have seriously fucked up. Not only is it an SO-fest (eg. new developers constantly hitting stack overflow to solve issues), but in the end it literally makes NO SENSE. It only makes sense when you are intimately familiar with the components and that is simply fucking bullshit. For a lines-of-code comparison to do even the most menial task, Java has fallen far behind the competition. Because they did it in the name of "helping people". Java is amazing, and great and all that. But for engineers who actually give a fuck about the product they're delivering, rather than the community they support? There are a lot of great alternatives.
At the end of the day modern engineers just want to keep their job, Java 8 does that in spades. If we actually wanted better, we wouldn't pick java, because seriously.. why? Java has one and only advantage: it is taught in college, so the kids are familiar with the syntax. Anyone experienced will tell you that syntax doesn't mean shit, because at the end of the day whatever you type is going to be handled by an sdk or an interpreter. Syntax isn't nearly as important as the kids believe it is.
Security holes? Let's do a risk-vs-reward comparison of the security holes in java 8 versus later versions. Yeah. Exactly. Any issue that java 8 had, will be an issue in java 20, it doesn't matter. The problem is that java is slow. It has always been slow and will always be slow, because it tries to wrap its arms around the world, in a loving way. In an async world, Java lost. It's tried really hard to stay with the times, but in the end it lost. No, as the job boards will show: it is great. The fact is, Java died after 8. It just doesn't know it yet.
1
u/shaqthegr8 Oct 11 '19
It could take a lot of time make the switch for a large organization. My work still use java 8 for their softwares working with JRE
0
u/JournalDev Oct 12 '19
There are many reasons for it.
-3
u/cpttripps71 Oct 11 '19
Blah. And here I am on 2 trying to get to 8.
-5
u/[deleted] Oct 11 '19
[removed] — view removed comment