[nonconvergent]

Java 8 is EOL in January for public support/security patches. Java 7 was EOL in 2015. What have you been doing for 3 years?

I could guess, because I've been at companies doing the same. Active development and support on the product, but no time for tech debt.

Java 9 and up I understand people getting frustrated with a more frequent LTS release and these weird microreleases every year.

[snuxoll]

Red Hat and AdoptOpenJDK will be supporting OpenJDK 8 for quite some time yet. Oracle's JDK and JRE will stop getting public support, yes, but OpenJDK 8 will be alive and well for many years to come.

[nonconvergent]

I was not referring to that. I was referring to the matter that they weren't ready to jump TO JDK 8 when JDK 7 was EOL, nor the next year, nor the next year after that.

What did they do with security updates when they were available for the version they were on?

Questions.

Don't get me wrong, they're not the only ones ice skating uphill on this.

[Zardoz84]

Sometimes it's your clients that are painfully slow to update. I know a client that (a few years ago), after a lot of issues and wasted time, we discovered that they had a Sun JVM 1.5 with some bug on String.length ! And the worse thing is that they not like the idea of update to Java 1.7

[_ea1k]

There are still plenty of systems out there on Java 7, usually due to external dependencies.