[ubertoop]

This is true in most languages really. It starts with people just wanting to speed up their development by turning common tasks into some macro, or annotation, or even library. But where does it end? It ends in a convoluted mess of dependencies, weird syntax, and hopeless stack traces.

So much work can be done with plain old Java. Or plain old JavaScript. Or plain old C + stdlib.

[jmartrican]

Agreed. Setting up Springs OAuth Client was so complicated and getting the configuration right was taking so much time. I replaced it with a simple Filter that just did the query itself. It easy to go to that filter and add whatever security logic you want (at least for me it is).

There is a balance here that might be hard to get right. Spring and other frameworks make things easier until they dont. At some point it might be easier to just write code instead of configuring your way through these frameworks. Many times I rather write code then go configuration hunting.

What I do like about Spring is that they offer a lot of hooks and interception points to overwrite with your own logic.

[ta988]

And you end up writing yet another custom framework for yourself when you realize you are writing the same things over and over...

[Pet_Ant]

But you and up writing just the bits you need so that you end up with a framework that serves your use cases, that you grew so you understand and unencumbured by the use cases of others. It'll make you more productive... but not necessarily the person you hand it off to.

[ta988]

Yes totally agree with that, it is not only negatives.