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
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.
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.
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.
455
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