Does your organisation get extended support from somewhere so that the JVM they use remains secure, or do they just YOLO it and use an ancient unsupported edition?
The weird thing is so many companies YOLO it with an ancient unsupported insecure version of the JDK, because they THINK upgrading is YOLO'ing it.
Somehow belief has settled in to many orgs that staying on ancient versions is good (stable, secure, proven, ripened like old wine), and updating is bad (unstable, insecure, unproven, unripe).
Even worse, this behaviour is likely to reinforce the idea that updating to a newer JDK is bad. Because when they do upgrade, it is more and more likely to take a lot of effort and break things the longer it takes between JDK upgrades.
New JDK updates are very cheap to upgrade to as long as you are on a recent-ish release already.
The point where many finally bite the bullet is when there's an incompatibility with a critical dependency they want to update to, and they can't hold off any longer.
Or when a horrible security vulnerability is disclosed that their organisation is affected by and the cries of "why did we not update sooner" go out.
It's like orgs that refuse to do backups because they are too expensive.
But, moving to a newer JDK is bad. Something always breaks. When we moved from 6 to 8 a lot of stuff broke. Same happened when we moved from 8 to 11. Now I'm afraid to move to 17, as again things will break.
65
u/joopmoore Mar 21 '23
Feeling a bit sorry for myself, I'm still internally pushing for the move from java 6 to a more modern version, but politics. I hope one day...