Quoth: “If Java EE is to survive as a platform,” (Werner) continues, “we have to stop teaching JEE as a set of JCP blessed related technologies…”

For JEE to stay alive, we have to stop the standardization process? Interesting.

He then sadly continues to point to AJAX as a success story - it’s free of committees, no organized process, blah.

Let’s rewind.

XmlHttpRequest (and varients) have been shipping with browsers for years, and it wasn’t until some Googlers discovered this useful little thing and lauched Google Maps did it become widely used.

The success of AJAX lately hinges on one factor: AJAX Frameworks making it again possible to develop JavaScript. They’ve eliminated browser differences for us; they’ve added convenience methods, event handling. We now have JS Debuggers, Request/Response Analyzers. You know, the tools one would need to write code.

For years, writing JS was horrific - and it wasn’t the fault of the language itself. It’s because the underlying DOMs of each browser/platform were so obnoxiously different that you’d be better off banging your head against a brick wall then figuring out how to make a DIV disappear.

Seems like some standardization of the DOM would have been nice. A committee of some type, maybe with representatives from Microsoft, Netscape, Mozilla. Or maybe if they listened to the recommendations of existing organizations instead of turning a deaf ear as if the W3C was the United Nations.

Proprietary “freedom to innovate” all but halted JS Development. Everyone ran their own direction, and ended up standing together wondering why they hadn’t moved.

But sure, let’s stop the standardization process in JEE. Maybe 5 years later a framework will come along that we can hail as the saviour of Java.

S,
ALR