There are pros and cons to both ways (aka convention over configuration). That is hiding configuration complexity often get fixed with even more internal comple

There are pros and cons to both ways (aka convention over configuration). That is hiding configuration complexity often get fixed with even more internal complexity except now it is hidden. With hiding configuration your ramp up time decreases but your overall understanding of how the library/framework may decrease. To offer the advantages of both requires even more complexity. Which is actually what happened with Spring Boot. It is the Ruby on Rails of Java now and it is far more complex internally than the olden days of Spring 2.0 explicit XML. At times I miss the old school Spring XML way. There used to be only like 4 tags (bean, property and include).