Interesting how much programmers care about the nuances of a language and don't bother to mention capabilities. GWT's main purpose is not to convert JS to a pr

Interesting how much programmers care about the nuances of a language and don't bother to mention capabilities. GWT's main purpose is not to convert JS to a proper language, but to provide a huge set of tools, like code generation for each browser, so you don't have to download code for WebKit if you're using IE, like you have to with jQuery. They probably chose Java to attract developers who are used to Java. Their Closure framework does the same things in JavaScript. JavaScript is also tied to a platform, a very important one. This means there is a big developer community making lots of libraries for the language, proper or not proper OO be damned. A bigger problem is the age, initial design criteria and currently limiting capabilities of the web. This is what a rethought language looks like http://blog.golang.org/2010/05/new-talk-and-tutorials.html http://blog.golang.org/2010/05/new-talk-and-tutorials.html http://stanford-online.stanford.edu/courses/ee380/100428-ee380-300.asx http://stanford-online.stanford.edu/courses/ee380/100428-ee3... Go solves far more problems than ECMA attempts to solve. The difference between JavaScrpit and C#, ActionScript, Java are minor. The real criteria is what can be built, how quickly, and how many people can use what's built. JavaScript is a workable language there, no less capable than Java because of some OO nuance. Go has the potential to make all these older languages look like toys, if you judge by it's capabilities instead of theoretical ideologies.