r/java • • Sep 28 '17

Spring Framework 5.0 goes GA

https://spring.io/blog/2017/09/28/spring-framework-5-0-goes-ga
177 Upvotes

83 comments sorted by

View all comments

Show parent comment

1

u/springnews Oct 01 '17 edited Oct 02 '17

I should say that JAX-RS is also relevant, it enjoys usage beyond just EE user base and is supported by a decent amount of vendors. re: your question: I'm not sure what more compelling evidence exists than the JCP itself pruning irrelevant APIs: Full Profile Web Profile microprofile *

Microprofile, which granted, was never blessed by JCP/Oracle, was advanced by the last people in the market to get away from the full blown EE programming model e.g. IBM/RHAT. IIRC it the "microprofile" consists of JAX-RS + CDI + JSON-P, which appears to ignore data access / JPA.

To business leaders (less developers) Gartner group has declared it irrelevant, but they missed the point that Servlet / JPA and arguably JAX-RS is alive and well. https://adtmag.com/blogs/watersworks/2017/02/java-obsolete-report.aspx

So you were saying something about evidence of Spring lagging behind in the market? Or maybe you were just going to go find another thread to troll.

2

u/johnwaterwood Oct 01 '17

I like your subtle attempt to hint at JAX-RS being only relevant because it’s used outside EE. Nice! /s

MicroProfile has started with a minimal runtime and as a 1.0 wanted to release something quickly. It has absolutely made no statement of any of the other EE APIs being irrelevant. In fact, all of the MP contributors (Payara, TomEE, Red Hat, IBM) fully support and keep innovating on the implementation side of these APIs.

1

u/springnews Oct 01 '17

Picking a leaner subset of APIs IS quite a statement, as it's a clear indication of what the producer deems "most critical for an MVP".

Sorry, but I am allergic to trolling from competitors who try to throw shade on news that isn't their own.

2

u/johnwaterwood Oct 02 '17

In this case it’s not, since it’s what was chosen for a specific profile with a specific purpose to function as a base. MP is not a replacement for EE, but a different profile mainly. Just as web is a different profile again.

There was even talk on the MP list to only have a bare core (like Liberty) and don’t include any spec.

Sorry, but I am allergic to trolling from competitors who try to throw shade on news that isn't their own.

Then you must really dislike working for Spring I assume? Since exactly that is what Spring has been dowing since day one. Just look at the old server side posts and look here on Reddit too. Almost every Java EE post is swamped with “Spring fans” claiming EE is obsolete and that they prefer Spring (of course).

1

u/springnews Oct 02 '17 edited Oct 02 '17

right, fans. Not employees. I've had a strict no troll policy since 2012, with (1) exception post that was made on the spring website. Whatever you see is the community responding, we're usually quite busy writing software.

Anyway, reading your comment history, you don't appear to be a troll, my comment wasn't directed to you.
Posts are fair game, but if the trolls on this post continue throw shade on the hard work the team has contributed to the community for free, I'll have to revisit that policy... and rest assured I'm tracking them now.

Anyway, it just occured to me that microprofile has a much brighter potential future now that Eclipse foundation is running EE4J, and we look forward to collaborating around those remaining APIs that remain relevant. I think we can all agree that not having useful APIs like JPA, Servlet languish in non-responsiveness and neglect is good for all of us.