The Spring framework is the most convoluted construct. You have ExceptionControllers that implement Abstractions which have other implementations themselves. You have ViewResolvers that have several different types, each of which has their own unique way of working. You have Configurers, Scanners.. anyway.

Even if it is excellent design, it's tiring to work with and understand, at least for my junior self. I used to kick ass on this stuff back at uni, but that was 5 years ago and I don't remember exactly how things work again, I'd need a refresher.

Thankfully spring boot and starters have made things a little better. Still have to roll with the paradigms though. 😀

Trust me, dealing with raw servlets and J2EE was worse.

@AlmondSauce That's exactly also what I did in 2012 when I did Programming 201; Servlets & JSP's.. I studied that stuff so hard I managed to get an A+ grade. The whole request and response thing.. .setAttribute, JSP lifecycle where the container builds subclasses and mixes logic, Sequence diagrams on that, explanations on how the container manages the lifecycle, taglibs, raw response writing, design questions, struts framework, patterns used, FrontController, Dispatcher, startup pages, RequestFilters, sessions.. the list goes on. A great adventure it was.

The only thing I find annoying is working with abstractions that lead to the well-known dependency hell.. or abstraction hell.

@CaptainPlanet
You probably already know about this, but just in case: https://www.baeldung.com/

@CaptainPlanet
nah, ignore the videos and tutorials, they're useless. They have a massive free set of docs for every feature in the Java+Spring ecosystem. Use a google site query to find the subject you want and you're good to go. 🙂

@CaptainPlanet
That is a great description of the Java ecosystem in 2020. Flavor of the month implementations, null annotation args, etc etc etc. There's a paradigm for every opinion.

@SortOfTested I use that website every day. :)