it's kindof funny the way frameworks/libs work My thought process using Spring in Java: 1. I should try to just use pure EE to leverage the power of the web c

it's kindof funny the way frameworks/libs work My thought process using Spring in Java: 1. I should try to just use pure EE to leverage the power of the web container so I don't include a heavy framework for no reason. 2. Now I have a need that pure EE doesn't solve so well.... Googling for solutions... oh look Spring framework can accomplish this. 3. I might as well go with Spring because it is well-maintained, convenient, & will probably solve some other utility needs that come up anyway. Better to have 1 solution than patchwork of several... 4. Well, now that Spring framework is installed I might as well just refactor some of this code to Spring, it will be slimmer... Same with jQuery.... if there is effort in learning compensatory methods for a various needs, there usually aren't many valid reasons for not just embracing a major lib/framework. (At this point I pretty much jump straight to step 4 as quickly as possible at the start of projects to avoid the refactor...)