> People who gripe about spring didn't bother to do things the spring way. Of course, everyone who complains about a technology just hasn't learned it properly

> People who gripe about spring didn't bother to do things the spring way. Of course, everyone who complains about a technology just hasn't learned it properly. I think I understand the Spring model fairly well at this point. But one of the problems with it is that it's confusing and that the runtime-reflection-heavy approach causes issues with debuggability, performance and also errors creeping into production that should by all accounts be preventable at compile-time. It's rather easy to make silly mistakes with Spring, such as confusing @Configuration and @ConfigurationProperties or writing tests that share the application context even though they require different configuration and suddenly stop working if they're executed in the wrong order, and even if you yourself learn it perfectly, your coworkers might not. I agree that it offers a ton of benefits - but that doesn't mean that it isn't valid to criticise it.