Just replied to ZDNet Article about Closure

by Mike Levin SEO & Datamaster, 11/06/2009

http://blogs.zdnet.com/open-source/?p=5220

If Google actually liked JavaScript so much, they would support it server-side by supporting one of the many endeavors going on, or creating their own. But they don’t. Almost none of their Google Data API’s are offered in JavaScript. Google’s love is for Python, and their official support is for Java and .NET because of the developer community.

Google’s apparent love for JavaScript is an evil born of necessity. The lingua franca of Web browsers is JavaScript, due to ancient decisions made by Netscape. We’re all just forced to live with it now, and Closure was something Google was forced into developing, so they could control the shared JavaScript libraries they used internally, and not rely on a hodgepodge of other libraries floating around.

Plus, Java isn’t really even underlying JavaScript as the “whose underlying Java language” statement implies. JavaScript simply adopted most of Java’s syntax to make developers feel comfortable, but the capabilities it offers, the way it runs, and almost everything about it is different. Syntax doesn’t make the language.

And finally, as to WHY Google released Closure, yes you’re right, it’s continuing the browser performance race that they started with the release of Chrome, allowing the web browser to be a viable alternative to an operating system—Netscape’s age-old vision reborn. And for that to be realistic, all the difficult aspects of programming in JavaScript need to be made easier by putting it under a unified un-confusing banner so developers don’t have to choose from dozens of semi-supported/semi-mature JavaScript libraries each time they start a new project.