Who told you that people are wary of updating Java?
I mean, I wouldn't want to use something in Production that didn't have an LTS agreement behind it, but that's not only limited to Java.
The main issue, is the security manager and Modules when moving through Java 9/10... but maintaining legacy projects always has legacy problems. All our newer projects are in Java 11 when deploying, or 14 during development (Maven profiles...). When we hear the next LTS release beyond 11, that will be our default - the next morning (and CI/CD will log tickets for projects that fail to build for some reason).
Challenging, yes, but wary?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Who told you that people are wary of updating Java?
I mean, I wouldn't want to use something in Production that didn't have an LTS agreement behind it, but that's not only limited to Java.
The main issue, is the security manager and Modules when moving through Java 9/10... but maintaining legacy projects always has legacy problems. All our newer projects are in Java 11 when deploying, or 14 during development (Maven profiles...). When we hear the next LTS release beyond 11, that will be our default - the next morning (and CI/CD will log tickets for projects that fail to build for some reason).
Challenging, yes, but wary?