Trust me, many companies cried in the bathroom when upgrading from 1.4 to 8.
Historical issues
The choice of JDK has a lot of legacy issues.
Many companies and even banks still use 1.2 and 1.4. This is because in many JAR development histories, there is no way to maintain the compiled JAR, and the old source code may not be able to compile with the new JDK.
If you want to upgrade the platform to 8, you must require that all the older jars be compiled with 8 once. Historically, this is unlikely, and the Maven platform didn’t exist in 2000. There was a lib directory in 2000.
With the current popularity of apis and microservices, new JDK versions will gradually be developed when migrating microservices to apis.
The current mainstream version is 8. If you use 11, it’s ok. The difference between JDK 8 and 11 is not that big, not as big as 1.4 to 8. It’s almost too big to compile with.
LTS versions
As many people know about the problem of LTS version, there are only two LTS versions in use at present, and version 17 has not come out yet.
Combined with the above two reasons, it is natural to choose stable releases when developing new projects.
The more stable the JDK is, the better.
In addition, the mainstream versions of OS installation are also these two. If it is a new project, there is no problem to use 11. If it is an old project that has already used 8, don’t think about upgrading. The support time will be the same anyway.
In fact, upgrades from 8 to 11 are not that bad, and are generally better.
www.ossez.com/t/java-jdk-…