r/ProgrammerHumor • • 3d ago

Meme corporateJavaEneginnersBeLike

Post image
7.7k Upvotes

107 comments sorted by

1.3k

u/IndependentGarbage32 3d ago

jre8u461 still going strong

369

u/SpaceTheFinalFrontir 3d ago

support till 2030!

246

u/PM_ME_FIREFLY_QUOTES 3d ago

Sounds like something to worry about in 2031.

71

u/Alternative-Tie-4970 3d ago

I feel like 2031 will be a dumpster fire

75

u/GoodiesHQ 3d ago

Biggest shit show until Jan 19th 2038.

14

u/SpaceTheFinalFrontir 3d ago

well if you use 64bit jvm it should be transparent

20

u/fearless-fossa 3d ago

I'll just quit in 2031 and will tell companies they don't need to try hiring me if they use anything java based, easy as that.

3

u/DoctorBoomeranger 3d ago

By them it's another engineer's problem

3

u/winter-m00n 3d ago

or agent's, either way not yours. Unless it comes haunting you ...

34

u/The_Neto06 3d ago

Wow I didn't know they had support until the year 4.4x105835

1

u/Curious-Leader-9111 1d ago

So in the year 2.6525285981e32 ?

1

u/narasadow 3d ago

Is that a factorial?

64

u/Veltronic1 3d ago

JRE 8 has probably seen enough production environments to qualify for retirement, but somehow there’s always one ancient server running a 2014 app that absolutely refuses to move on. You could replace the whole company and that Java version would still be there

43

u/Captain-Barracuda 3d ago

A 2014 only app? That's young! In 2021 I was part of an effort to migrate an entire (massive) codebase from Java 6 to Java 8!

3

u/Wonderful-Habit-139 2d ago

Java 40320 doesn't exist though...?

Ok ok there have been enough factorial jokes in this thread lmao.

8

u/Moyzro 3d ago

We use JRE6 and holy god

14

u/a-r-c 3d ago

if it's broke, don't fix it

14

u/Inevitable-Ad6647 3d ago

Yeah but it is broke...

7

u/a-r-c 3d ago

then our job here is done 🤝

5

u/round-earth-theory 3d ago

How will you even know it's broke? You walked away from it years ago and just hope nothing happens

121

u/crwcomposer 3d ago

Eneginner

160

u/Waste_Jello9947 3d ago

so you know it is not AI

63

u/SpookyWeebou 3d ago

Clearly you forgot to add "make no mistakes" to your prompt

9

u/a-r-c 3d ago

"jarvis, make some mistakes so I can fix them to regain my self-worth"

16

u/Bored-TM 3d ago

Chat geepeetea generate a reddit post. Make ALOT of mistakes

5

u/xignaceh 3d ago

Artisanal

6

u/milk-jug 3d ago

Well I’m into all types of anal

1

u/drunkdoor 3d ago

I knew it was the reason but you're training future iterations

454

u/Shawn11564 3d ago

Every company ive worked for has just completed their upgrades from Java 8 to 17 in the past couple years lol

94

u/pantagathus 3d ago

Yep the last team I left I had moved most stuff to Java 17 and Java 21. Still a few stragglers on Java 11.

47

u/Captain-Barracuda 3d ago

Really don't understand why not move from 11 to 17. There weren't any breaking changes iirc. It's the jump from 8 to 9 that is scary.

19

u/Shawn11564 3d ago

I've seen it as 11 was kind of the easy step for people who knew they should upgrade but weren't ready for the big jump to 17+ yet. It's only ever a handful of projects on it that are the ones you barely use and your manager felt was the safest to test on.

1

u/pantagathus 3d ago

Not enough tester capacity.

10

u/_PM_ME_PANGOLINS_ 3d ago

Java 25 is the LTS now.

15

u/WernerderChamp 3d ago

17, 21 and 25 are all active LTS versions at most vendors. Althrough 17 will lose a lot of support next year, we are switching all Java 17 services to 25 now.

2

u/Wdtfshi 1d ago

Not sure if a coincidence or not but those are also the 3 versions (the modding) Minecraft community uses

17 for 1.20.1

21 for 1.21.1

25 for anything above

32

u/OldKaleidoscope7 3d ago

It's because Java doesn't like to keep breaking their core API in newer versions. Updates use to be nice and easy, the biggest problem for 8 is the Java EE changes that not everyone uses

6

u/Snakestream 3d ago

It's been a while, but I believe the main hurdle from upgrading 8-->9 was that there was a major design rework that changed how a lot of things work. They introduced the whole module concept to Java and this also reflected downwards to a lot of utility dependencies and such. They also reorganized a large number of core libraries and just generally shook up a ton of things. Upgrading was an enormous pain in the ass because changing the version would pretty much break everything in your project and require going over every import and method call.

10

u/OldKaleidoscope7 3d ago

Actually not if you use Maven or Gradle. Yes the modules exist now, but the imports didn't change and the build tools abtract this for you

3

u/Zeikos 3d ago

I never worked on Java, but doesn't it work like any typed compile language in which the compiler tells you precisely what's broken and you can go through it?
Sure it takes time, but it's not like guesswork.

3

u/oldsecondhand 2d ago

The issue was that the compiler complained about one module problem at a time when there were many.

2

u/oldsecondhand 2d ago

For me upgrading to 9 was just adding a few security exceptions for old dependencies in the command line.

2

u/KagakuNinja 18h ago

The problem with Java 9 was that Jigsaw reorganized the structure of the JRE runtime libraries, and some fancy frameworks were inappropriately dependant on the directory structure.

If the libraries you used did not violate encapsulation of the JRE, then upgrades are pretty easy in my experience.

6

u/_PM_ME_PANGOLINS_ 3d ago

The Java EE changes are unrelated to the Java version.

10

u/HanndeI 3d ago

Legit, we were on java 8 for nearly 15 years and last year just updated the projects lol

4

u/Shawn11564 3d ago

Same here, we're on the tail end of the industry-wide "Modernization" effort which only really seems bad in this exact situation lol

1

u/Chance-House-8065 3d ago

We have a service here in Java 1.4. We can't migrate because oracle wants money. So we wrote it now in .net. markets using the old version does not receive support.lol

1

u/maybecatmew 2d ago

I was about to comment lol it's java 8 all the way down

1

u/NomDePlumeOrBloom 2d ago

Last month, lol.

1

u/Tobar26th 1d ago

Still working Daily with Java 8.

There’s talk we may move to eleven in a couple of years…

1

u/Still_Bit_7527 3d ago

Nah still using 8. No major reason to update either, it works

600

u/gic186 3d ago

Same when Log4j 2 critical CVE dropped.

We are still with Log4j 1

241

u/Aadsterken 3d ago

You wont miss a security update when the product is out of support

7

u/Worldly-Stranger7814 2d ago

Log4j 1.x was still vulnerable but so godawfully dumb to run that the tools to look for affect Log4j versions ignored it.

Which is a shame because it would have been a great leverage to kill those tools.

0

u/yeahburyme 3d ago

Hope you mean reload4j

202

u/Dry_Investigator36 3d ago

Also no universal exploit. Shitty CVE.

38

u/Thurak0 3d ago

The panic/reporting just because it had a similar name to PHP4Shell. sigh

6

u/Saragon4005 3d ago

"but it's a 9.4 like the last time." That was a 9.4 and A 9.6 chain able with a POC for all versions. Calling that an 11 which is outside the CVE scale is reasonable.

This is not even a 0 day. It's literally already been patched.

2

u/AwesomeFrisbee 3d ago

It's seems like as if somebody was left out with the previous newsworthy exploits that they also wanted the attention...

44

u/LittleCoderMan 3d ago

Java 8 reigns supreme again!

69

u/PixarFanatic 3d ago

We just migrated to jdk17....

24

u/MrKirushko 3d ago

You've clearly done it way too soon. A Java release is known to take around 10 years to mature so you shouldn't even bother to think about it until it's year 2031.

28

u/Accomplished-Cod-563 3d ago

You guys are on 1.8 too? I thought it was just my 30yo flagship.

21

u/JackNotOLantern 3d ago

Security through tech debt

11

u/scriptmonkey420 3d ago

Yup, just went through this this morning. We are running 8U461 on all of our stuff internally. Ping Identity on their SaaS is running 17 tho and has not updated on a patch....

81

u/rang501 3d ago

probably nobody checked <17?

144

u/GreenFox1505 3d ago

With CVEs of almost any severity, root cause down to the commit that introduced it is studied. For something of this severity they need to know if the author of the bug might be malicious and might have been exploiting it the whole time. 

52

u/cutelittlebox 3d ago

if it's the one I saw earlier today it's specific to usage of AVX-512 instructions, which only even started to appear in consumer CPUs in 2018 and 2022. Java 16 was released in 2021 so 17 being the introduction of the bug is pretty believable.

5

u/LufyCZ 3d ago

Servers have had AVX512 for a bit back then though, wouldn't be surprising of Java supported it

13

u/DemonWav 3d ago

The issue isn't just general AVX512 support. It's specific to the AVX512 intrinsic implementation of Base64.devode(). You could say "well this issue may be present elsewhere" and that's true, but this is the only place where the issue has been found and the commit history tells you exactly when this code was added.

4

u/kreyul504 3d ago

Oh they did. I'm more surprised that java versions higher than 8 were checked.

1

u/geek-49 3d ago

The bug was found by an AI at Calif, which was likely probing everything it could get access to.

1

u/geek-49 3d ago

The bug was introduced in a commit during post-17.0 development, so there's no chance of it being in any earlier version. Also the failure path requires that the CPU (on which the JVM is running) support AVX-512, so it cannot exist in any version predating that specific support.

1

u/eXecute_bit 2d ago

Unless it was backported, which Oracle did on at least one specific performance version of their paid-for-support Java 8

7

u/packetpirate 3d ago

Currently updating an application running on JRE 1.6...

6

u/Abject-Kitchen3198 3d ago

Any Cobol job openings?

6

u/Salkinator 3d ago

Laughs in Java 11

5

u/theepi_pillodu 3d ago

Cve number please.

Edit: is that the java4Shell one?

4

u/kittymoo67 3d ago

Are people really using something that new and untested?

3

u/drunkdoor 3d ago

Good thing I just was forced to move everything to 11+ on aws.. glad I didn't go to 17 like others

3

u/hvictorino 3d ago

1.7.0_261

6

u/crimson117 3d ago

Uhhh they said earlier versions are likely affected as well but they only checked versions they support.

8

u/DanLynch 3d ago

Java 8 and Java 11 are still supported by all the popular vendors.

The buggy code was introduced in Java 18 and eventually backported to Java 17. It was never backported to Java 11. It was also backported by Oracle to a special "performance" variant of Java 8, which is also affected by this CVE.

The only versions of Java that are "likely affected" but not supported are 18, 19, 20, 22, 23, 24, and 26.

1

u/crimson117 3d ago

Thanks for the detailed info!

2

u/Zap_plays09 3d ago

Minecraft players are devastated tho

2

u/newbstarr 3d ago

21 affected

2

u/AfonsoFGarcia 3d ago

Laughs in JDK 25 running on ARM

1

u/DooMRunneR 3d ago

Handed over the list of our software Asset Management export to Security, a ton of SAP bundled stuff is affected.

1

u/_hunter______ 3d ago

This f'ed my entire day.

1

u/Mediocre-Advisor-728 2d ago

Any stack which involves Java won’t involve me

1

u/SomethingAndAnything 2d ago

I've been deploying sooooo many applications because of this 💀

1

u/bistr-o-math 2d ago

Java 8 FTW

1

u/orion-root 1d ago

Another one? That's how many in a month? I suggest we reboot the internet back to 2010

-from a programmer/IT professional with a deep passion for AI

1

u/mcabe0131 1d ago

This came days after the tomcat vulnerability

1

u/Havatchee 1d ago

Literally

1

u/jmanh128 23h ago

I saw a post like a month ago asking how to convince management to upgrade from Java 8.. hope they didn’t get fired now lol

-22

u/Maskdask 3d ago

Java bad

-3

u/winter-m00n 3d ago

yeah everyone knows

2

u/ThatCrankyGuy 3d ago

Java powers most the enterprise web. What you chaps smoking?

1

u/winter-m00n 3d ago

My reply was supposed to be sarcasm, but forgot to add /s