This is absolutely spot-on. The concepts that Johnson & co coalesced around, mainly IoC, DI, interfaces, and layers, are bedrock foundations for how most people write any service-oriented system. Say what you want about the things that Boot itself does, like auto configuration, or the Data persistence abstractions, but the foundations of the library are bedrock software engineering, so if you're gonna dump on something that's proven over 20+ years, you better come correct.

This "lingua franca" of Java development also allows you to hire, onboard, and get people productive - rapidly.

> It's plain this person lacks the experience and perspective to appreciate the problems a stack such as Spring solves

lol, having worked in Spring codebases for over a decade at this point, I assure you those of us who dislike Spring know exactly what problems it "solves" (which, btw, it doesn't)

if you can't seriously acknowledge and understand the mountains of criticism that has been leveled against Spring, by experienced and novices alike, you're the one who is arrogant and needs a reality check

but yeah it's typical of Spring fans to portray it as if Spring is The Only Professional Option when in reality there are much, much better, easier and simpler solutions for the same problems out there, including eg DropWizard and Ktor

"This person" makes rather relevant comment on Spring boot's severe shortcomings.

Whereas your comment from throwaway account is blabbering nonsense.

Well that supports my point actually, that these "short comings" aren't short comings at all if one takes the time to learn the framework. Blabbering? People often say that who have no valid technical or intellectual response.

I don't see anything beyond ad hominem. That reveals more about yourself than you probably think. I'll move on then.

Why would framework be correct if the premise of heavy runtime reflection based approach itself is bad?

You can spend your lifetime learning this framework, others can simply reject on first principles' basis.

> Why would framework be correct if the premise of heavy runtime reflection based approach itself is bad?

Because the framework allows zero reflection approach.

Their comments on the shortcomings boil down to, "I didn't spend any time learning how this works."

Things like these (https://news.ycombinator.com/item?id=37839306) are not solved by "learning how it works". Nice try to attack my competency tho