24 September 2007

Isn't Web Beans not just a little embarrassing, but an extremely painful admission for the Java world? Do not read this as an attack on Web Beans itself, but the implications represented by its mere existence. What problems is it solving? It is a solution for JEE 5's current complexity, which was (JPA in particular) drastically re-engineered from its previous iteration. So it provides a unification API for existing APIs, which was an abstraction of previous APIs, and so on. Rinse, repeat.

Isn't this a bit like grasping for straws when the only straws left are the short ones. Arriving far after 'eeny, meeny, miny, moe' has already pardoned a few. The community is left to deal with the grand unified results, only to face another abstraction a year later because the current API isn't 'simple' enough.

Which reminds me of another nursery rhyme. Even a leather shoe is edible with enough boiling and gravy. But that doesn't mean you should eat it.

There was an old woman who lived in a shoe.
She had so many children, she didn't know what to do.
She gave them some broth without any bread,
Then whipped them all soundly and put them to bed.

Hmmm, interpretation is left as an exercise for the reader.