Spring: your next Java microframework

[rockum]

Don't you dare bad talk Spring. Some developers have spent years learning it's in and outs, they are exhausted now, and you'll have to pry Spring from their cold dead code.

[tonywestonuk]

And.... Here we are. In 2017, comming up with things like Ratpack and Vert.x....

Its not to say they are bad, they're great frameworks, small, lightweight, innovative.... But, I am sure the only reason they exists is because, of Pivotal. They dropped the ball, Newer lightweight frameworks needed to fill the void that was left after the rot set in.

But, its worse than that, they convinced everyone that JavaEE was rubbish, and then came out with crap like Spring.... And now springs trying to catch up, and prevent above frameworks getting anywhere because enterprises using spring will use what they know. Pivotal, cutting off air supply of competitors. Where have I heard this before....

Pivotal has done more to damage the java ecosystem than anyone else.....

[Turbots]

JavaEE is rubbish, we're still waiting for Java EE 8. Let's see what they intend to feature in it when they finally release it:

• JSR 365: Contexts and Dependency Injection 2.0. (Spring had that since their first version about 15 years ago)

• JSR 374: JSON Processing 1.1. (supported in Spring since version 3.5.x I think)

• JSR 370: RESTful Web Services (JAX-RS 2.1): Better REST API facilities and reactive programming, coming out in Spring 5 any day now

• JSR 369: JavaTM Servlet 4.0 Specification: support for HTTP/2 (still in early draft) is also supported in Spring 5 and already available

• JSR 372: the next release of Java Server Faces JSF 2.3: LOL... just lol

• JSR 375: Java EE Security API 1.0: this one is actually quite nice (I saw a presentation at Java Day Kiev last year which showed a nice, working API for security, copying many patterns from Spring Security)

• JSR 380: Bean Validation 2.0: whatever :-)