Chapter 1. The Inevitable Bloat
Java development is in crisis. Though Java's market
share has been steadily growing, all is not well.
I've seen enterprise Java development efforts fail
with increasing regularity. Even more alarming is that fewer and
fewer people are surprised when things do go wrong. Development is
getting so cumbersome and complex that it's
threatening to collapse under its own weight. Typical applications
use too many design patterns, too much XML, and too many Enterprise
JavaBeans. And too many beans leads to what I'll
call the bloat.