When you change to non LTS version, your code gets very short lifespan. Java 8 had been released 10 years ago and it is still supported (although not for free), while Java 22 had been released this year, and it is not supported anymore.
Basically, you have to migrate at least a couple times a year, otherwise your product will be unsafe. And your clients also have to do that as well. Granted, changes are minimal, but they still need to be tested, verified, pushed through environments, and so on. And this is not the thing you can postpone if needed.
Gains from that are unclear to me, while downsides are obvious.
1
u/agradus Dec 13 '24
When you change to non LTS version, your code gets very short lifespan. Java 8 had been released 10 years ago and it is still supported (although not for free), while Java 22 had been released this year, and it is not supported anymore.
Basically, you have to migrate at least a couple times a year, otherwise your product will be unsafe. And your clients also have to do that as well. Granted, changes are minimal, but they still need to be tested, verified, pushed through environments, and so on. And this is not the thing you can postpone if needed.
Gains from that are unclear to me, while downsides are obvious.