What? Why are you using this ancient stone age technology like Java 8 in 2023? I thought this was going to be about the new integrated Spring Boot docker functionality of 3.1.
Oracle will be supporting Java 8 for 7 more years! All the fortune 100 companies I consult for use Java 8, too many legacy libraries to upgrade for a newer version. Even Spring Boot 3 does not work with Java 8. It's impossible to move to a new version of Java until all the companies can upgrade (or are forced to based on support). Trying to upgrade and have Security teams approve the change is all but impossible. Too many people want to stay in the 10 year old eco-system, DevOps teams always push back on upgrades. Now that we have more and more Microservices it really do not have the same issue any more but in reality Amazon is only at Java 11 (Lamdba, etc) and Spring Boot 3 requires Java 17. Even after Oracle saying they will not charge for Java now there are so many things stopping progress. Even with all the security issues in Legacy Java it has not been push forward. It would be great to have Records and all the new features but the simple changes of javax.* to jakarta.* in Spring Boot 3 kills so many legacy libraries that it will be a major update to move to Spring Boot 3.
Amazing how fast you can create a Docker Image for a Spring Boot Microservice. In less than 10 minutes!
What? Why are you using this ancient stone age technology like Java 8 in 2023? I thought this was going to be about the new integrated Spring Boot docker functionality of 3.1.
Oracle will be supporting Java 8 for 7 more years! All the fortune 100 companies I consult for use Java 8, too many legacy libraries to upgrade for a newer version. Even Spring Boot 3 does not work with Java 8. It's impossible to move to a new version of Java until all the companies can upgrade (or are forced to based on support). Trying to upgrade and have Security teams approve the change is all but impossible. Too many people want to stay in the 10 year old eco-system, DevOps teams always push back on upgrades. Now that we have more and more Microservices it really do not have the same issue any more but in reality Amazon is only at Java 11 (Lamdba, etc) and Spring Boot 3 requires Java 17. Even after Oracle saying they will not charge for Java now there are so many things stopping progress. Even with all the security issues in Legacy Java it has not been push forward. It would be great to have Records and all the new features but the simple changes of javax.* to jakarta.* in Spring Boot 3 kills so many legacy libraries that it will be a major update to move to Spring Boot 3.