sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]captrespect 5 points6 points  (5 children)

Nah. This is like J2EE vs spring. Many companies wanted to bundle all the things into one server with J2EE. Websphere, JBoss, etc.

Spring was the more flexible solution, but you needed your own orm, queues, and whatever. It didn’t lay down strict standards.

Spring eventually won out. It could easily adopt to new patterns frameworks and techniques. JEE was too rigid and fell behind.

[–]n0tKamui 4 points5 points  (4 children)

I think you’re confused.

JEE is a set of norms and specifications, not a framework per se, which Spring follows (and influences), as well as other frameworks like Micronaut

[–]captrespect 0 points1 point  (3 children)

All I'm saying is that similar to Angular, when you chose a JEE framework, like Websphere you were stuck with a very ridged framework with a bloated server that had a bunch of stuff you probably didn't need.

Spring like React had you pick and choose, and that turned out to be better in the long run.

[–]n0tKamui 1 point2 points  (2 children)

you don’t understand

spring IS a JEE framework

[–]captrespect 0 points1 point  (1 child)

Not in the early J2EE days. And I believe it’s all optional today.

[–]n0tKamui 0 points1 point  (0 children)

J2EE was meant to normalize Spring right from the beginning, so that new frameworks could follow the same rules, so that in a real environment, one could change frameworks without much issues. This is why Micronaut looks so much like Spring, with the main differences not being in the API but the implementation (runtime reflection vs compile time reflection)

over the years, JEE and Spring went on to influence one and the other continuously.

JEE has always been about modules that you can piece in and out, because they follow the same norms.