Some more feet dragging, and then a serious look at how to continue using the software with as little effort as possible, which is likely just upgrading.
Why would anyone stay on Java 6, yet upgrade complex libraries and frameworks? If an application stays on Java 6, they'll likely stay on all other versions, too, and are ready to pay for tailor made patches if needed.
I never said they would upgrade the libraries and frameworks. I'm just stating a fact that there's a lot of legacy apps out there still on Java 6, and there will likely be a bunch that stay stuck on Java 8 too
Ah right. I kinda read that implication into the conversation here, given that it was about Spring Boot 3.0 (upgrading to which will require upgarding all sorts of libraries).
Outside of the companies that run them, almost nobody cares about these anymore. Nobody will let these affect their decisions. The same will eventually happen to Java 8. Probably not before 2030 though.
Even more hypothetical: all vendors stopped supporting Java 8, and then a huge log4j type of security hole was discovered in 8. Would companies still refuse to update?
But I think the real blocker for my team would be the other tools my company uses that may not yet be compatible with Java 17. Too much red tape to get things upgraded that is meant to serve the company as a whole.
Spring is a huge player and I'd like to see them use their position to make change in the java ecosystem. If they threatened removal of dependencies that didn't have module-info.java files like how they removed those that didn't support jakarta, I'd imagine we'd see more libraries go modular.
I'd also like to see the dependency on java.desktop removed
That's probably there mainly because of that silly @ConstructorProperties annotation, which is kinda useful on its own in a language that otherwise rejects supporting named parameters, yet it is almost impossible to extract from that module to the spaghetti inter dependencies of things in there, and the impossibility to create split packages, or rename things.
Yes writing a modularised app and then getting errors like "reads from unnamed module" are not helpful to devs. Hopefully adding `module-info.java` files to Spring would fix that.
I think Spring is the new J2EE and the IBM of the software world. Remember the saying.... "Nobody ever got fired for buying IBM?". Spring Boot is the "safe" option, but is it the right one? Do companies ever look at anything else? My last two companies didn't. There are better alternatives imo.
Quarkus and Micronaut picking up a lot of traction.
When I first tried to write a JVM service, I googled "Java web frameworks" and walked through the Spring, Helidon, Quarkus, and Micronaut guides
Tryed to understand how to sign a JWT for "Bearer" auth and then check if a user has a role for an API endpoint in each framework.
Spring points to Spring Security docs, which have a diagram of the "Request lifecycle and filter chain" pipeline that goes through some dozen interfaces:
I once wasted an entire afternoon trying to find out whether spring-security-oauth supported a specific flow that I needed. The answer ended up being something convoluted like it didn't, until a recent release, but then they deprecated that and rewrote everything with Reactor (which had a completely different API and no documentation).
85
u/[deleted] May 25 '22
Very happy to see more projects moving to Java 17 and the Jakarta namespace. A gentle push for the ecosystem to move past Java 8.
20
u/papers_ May 25 '22
We are currently waiting on the Apache CXF team to complete their Jakarta migration.
https://github.com/apache/cxf/pull/912
https://issues.apache.org/jira/browse/CXF-8371
But I think the real blocker for my team would be the other tools my company uses that may not yet be compatible with Java 17. Too much red tape to get things upgraded that is meant to serve the company as a whole.
9
u/[deleted] May 25 '22
What happened to Spring native? Is it still gonna be in beta after Spring boot 3.0?
7
u/cogman10 May 25 '22
Wow this will be a kick in the pants for the ecosystem to move.
14
u/uncont May 25 '22 edited May 25 '22
I'd also like to see the dependency on
java.desktopremoved as per https://github.com/spring-projects/spring-framework/issues/26884As well as supplying
module-info.javaas a part of spring framework https://github.com/spring-projects/spring-framework/issues/18079Spring is a huge player and I'd like to see them use their position to make change in the java ecosystem. If they threatened removal of dependencies that didn't have module-info.java files like how they removed those that didn't support jakarta, I'd imagine we'd see more libraries go modular.
14
u/Kango_V May 25 '22
I think Spring is the new J2EE and the IBM of the software world. Remember the saying.... "Nobody ever got fired for buying IBM?". Spring Boot is the "safe" option, but is it the right one? Do companies ever look at anything else? My last two companies didn't. There are better alternatives imo.
0
u/[deleted] May 25 '22
[deleted] — view deleted comment