Saving J2EE
J2EE is topping out.
Here's the evidence....
1) In the misc.jobs newsgroups, J2EE shows a technical analysis pattern of steadily declining peaks:
Click for larger image
2) Saturated markets shift their focus from differentiated features to cost consciousness.
Low-cost JBoss steadily gains mind share:
Low-cost JBoss steadily gains mind share:
Click for larger image
3) High cost J2EE tools are abandoned for cheaper alternatives.
Eclipse is leading all other tools, but even Eclipse shows a pattern
of a slowing growth rate:
Click for larger image
4) A rising competitor
(according to ActiveGrid.com) with an accelerating rate of change.
(Linux, Apache, MySql, Perl)
(Linux, Apache, MySql, Perl)
Click for larger image
So. How do we save J2EE?
Should we even try?
First, let's look at a transaction cost concept... The Mythical Man Month.