3 ms·
Java has an almost unbroken history of hassle-free version updates, all the way back to Java 1.0. (Okay, okay, I know you have a specific anecdote of a broken v
by stevoski 2y ago
Java has an almost unbroken history of hassle-free version updates, all the way back to Java 1.0. (Okay, okay, I know you have a specific anecdote of a broken version update. I said “almost”.)
The one major exception was from Java 8 to Java 9. There’s some good reasons why Java 8 to Java 9 wasn’t a smooth upgrade for all. But that’s a story for another day.
For slow-moving enterprise IT departments, that would involve a major “update Java” project. Which involves budgets and people and not doing other things in the meantime.
Hence why Java 8 is still so prevalent in enterprise world.
- tpm 2y agoI don't even remember Java 8 to 9 (our platform vendor updates his product and after that we have to update ours in a fairly short timeframe, so it must not have been too painful), but I think there is a breaking change in every recent release, most recently we had to rename javax.mail to jakarta.mail and some other stuff like that when upgrading to Java 21. I don't mind but would not describe that as hassle free.
- 62951413 2y agoIn a galaxy far far away so called "J2EE application servers" used to be the reason JDK upgrades were not allowed. And that would probably be a real major update Java project. When I joined my current team (in a big honkin' corporation with a history of layoffs and outsourcing) I inherited a dozen microservices, all on JDK8 and a couple written in Scala. So among the first things I did was an upgrade to JDK17 of every single repository. And it was mostly uneventful. More or less use a different Docker base image and bump up the Spring Boot version from 1.x to 3.4. Not running the latest LTS release is professional negligence in my book.
- deleted 2y ago[deleted]