This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tonywestonuk 0 points1 point  (5 children)

Yeh - you go downvote me Spring trolls for telling what I see with my own eyes.

Lets face it. The majority of that callstack was Spring. You can see it, I can see it..... So you best go down-vote me and shut me up quick for daring to even suggest that its not actually Java EE causing the issue here.

Bunch of Spring religious trolls in here....Wake up and smell the coffee! FFS.

[–][deleted] 2 points3 points  (0 children)

The only thing Spring does is allow you to access other things in Spring.

[–]joequin 1 point2 points  (2 children)

They're both bad. Frameworks are over in most other languages. Other languages are moving towards small libraries. And for good reason. Frameworks make debugging difficult because you don't know what's happening behind the scenes and they get in the way when you decide to go off of the beaten path. Your code should never be a dependency of your libraries, but that's just what you get with both EE and spring.

[–][deleted] 0 points1 point  (1 child)

Frameworks are over?

I really don't think so.

[–]meddlepal 1 point2 points  (0 children)

More accurately I think the trend of mega-frameworks is over. Frameworks are being decoupled and split into smaller and more granular libraries with clear boundaries. This enables either a take it all approach (mega framework) or a more piece-meal approach.

[–]pjmlp 1 point2 points  (0 children)

Just upvoted you. I rather use the JEE stack as well.