deepthoughts.orsomethinglikethat

I'm not against acronyms, but recently I stumbled upon the Java Community Process (JCP) Wikipedia article, while looking up what exactly JSR (Java Specification Request) stands for. The JCP article lists all (or at least some - I don't know) of the JSRs that exist; including their number and technology...

RTSJ, JMX, JAXP, JDO, JCA, EJB, CLDC, JAXB, JSIP, CDC, MIDP, JMI, NIO, JSTL, JSP, JDBC, JNLP, JDM, JAXR, JDOM, WSDL4J, WMA, JSF, MMAPI, SLP, SDP, JCR, SATSA, SIP, JTWI, NIO2, JBI, JAX-WS, XQJ, SDO, JDM, MTA, IMS, JTA

Oh oh... looks like I forgot one... JBS

This is in response to Michael Urban's posting, "And The Fastest Growing Web Framework Is..." (which is also kind of a commentary/response to a Rick Hightower blog posting) which awards the honors to JSF based on job posting trends from February 3, 2005 to June 27, 2007.

I won't argue that the job trends chart clearly shows that JSF has had a significant number more job postings for the last two and a half years. You might argue the means the data was gathered but that's already been done extensively in the article's comments.

I will offer an alternative (I'll admit a bit ridiculous) interpretation that states the reason there are so many more JSF job postings is because JSF is the least productive web framework listed; requiring more developers to complete a project. I know it's another poor conclusion drawn from the chart, but I would venture to say that the average JSF project's development team is larger than other development teams using the other listed web frameworks.