Could you please discuss any similarities and/or differences between the Spring approach versus the Jakarta EE approach? For example, doesn't Spring always have the disadvantage of continually needing to catch up to the latest Java (and/or Jakarta EE) specifications? Or are both technologies evolving and "learning from each other" over time? Are there certain areas of Jakarta EE that Spring will never "catch up" to?
I have been using Spring in a Java Enterprise environment since it was J2EE. I never considered it an either/or situation. Spring Data makes an excellent backend for JavaServer Faces webapps. I've used Spring features like Spring Batch, Scheduling, and email services as well.
In any event, chances are you'll find people from Spring involved in the Jakarta JSR processes and Spring has always been kept aggressively up to date.
I'm going to be a "small government" candidate. I'll be the government. Just me. No one else.
In short, where it makes sense, Spring will leverage work done in other projects, including JakartaEE.
That said, Jakarta EE as a whole attempts to create its own mega-framework that can be seen as competing with Spring. To be honest, I've not had much opportunity to consider Jakarta EE as a whole lately. What I do know and believe is that Spring is moving faster, covers more ground, and is more innovative than what I've seen in Jakarta EE. I don't say that to pick a fight...if you or anyone disagrees, then that's fine and I won't be dragged into a Jakarta EE vs. Spring debate. I'm just saying that from what I've seen and experienced, Spring is the best choice for enterprise and cloud development.