The problem is not the system; the problem is education.
“The problem is not the system, its the way someone can get in. To be honest, most tutorials, how-tos, and documentation sucks, because they ALL are written like the reader already knows the trick. No doc about [Technology] is written for newbies.”
Technology == “EJB”
Technology == “CDI”
Technology == “JSF”
Technology == Education
It is clear to me that the gap in our Java EE community is not a fault of the technology. The technology is quite simple (as I learned while doing a deep port of a Spring-based app to Java EE.)
Just as I think the future of the United States of America is in jeopardy because of budget cuts in education and health care, the future of Java EE is in jeopardy because nobody is willing to pay for any kind of decent, centralized, use-case driven documentation and examples. Teaching by example that is done so well on http://php.net and http://playframework.org; Java EE is the largest web-framework without a home.
Education is always 95% of the solution. We already have the technology, but if nobody can figure out how to use it, then nobody is going to use it; and let me tell you, it’s not that hard once you know “the trick.”
Who’s going to step up and claim a few hundred thousand page-views per month?
Technology == “Java EE”
Posted in OpenSource