If you vote you can be DZone's BFF! Login and vote now.
By rnocera
via java-hair.com
Published: May 06 2008 / 15:54
My last post about frameworks criticized the Spring JDBC Template construct. I don’t really have anything against Spring in particular. My point, which I attempted to illustrate by that post is that frameworks in general, which exist to simplify development of complex technologies, by their nature redirect that complexity somewhere else. As an architect/designer/developer you should be aware of that the trade-off exists, what the trade off is going to be and make an informed decision.
Comments
Gregg Bolinger replied ago:
Voted down for the lack of any new information. This same type of debate seems to go on and on and folks always mention the same frameworks over and over causing these debates (Struts, jsf). Just stop using crap frameworks and your problems decrease.
rnocera replied ago:
the article doesn't debate the matter of the different frameworks, it simple points out that ALL frameworks have these types of problems. I haven't found one that doesn't yet, have you?
fmoidu replied ago:
There is no silver bullet. Thats a known fact.
The article doesn't present any new information. It just skims the top of already known issues. Whats the point of re-reading something thats already been covered ad nauseum?
Voters For This Link (9)
Voters Against This Link (2)