> There are many people who don't have any problems with Spring. They might not love it but they don't hate it also. A lot of “enterprise” developers don’t car

> There are many people who don't have any problems with Spring. They might not love it but they don't hate it also. A lot of “enterprise” developers don’t care. There are many reasons for this, some positive, some negative. But one outcome is that Spring becomes self perpetuating. Eg a new tech lead inherits a Spring project. Then at hiring time it becomes easier to ask for Spring experience. This drives an industry perception that you gotta know Spring. The costs — overly complicated code, ridiculous startup times & containerisation cost, messier dependencies, are often ignored or hand-waved away saying “this is the cost of enterprise”. (It’s not.) This is not to say Spring is inappropriate in an enterprise. What I am saying that many enterprise teams do not often have that cost/benefit conversation, instead they reflexively adopt Spring. That is the real problem.