Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In November 2009 Google announced the release of Closure Tools which include the Closure Library.
According to this post google closure library contains some battle-hardened parts and others more experimental.
Could folks with experience using google closure share info on which parts are solid and which are iffy(er) or not ready for production use? Some demos apparently don’t work in latest firefox (as of January 2010).
The Closure Library is a JavaScript library that’s
Lower-level utilities for
Basically the compiler portion compresses your JavaScript logic into smaller code area that is compatible with a wide array of browsers, removes dead code, etc.
The Closure Inspector, a tool that makes it easy to use the Firebug JavaScript debugger with the Compiler’s output.
And you basically get a good portion of what Google needs for itself to develop with – I love all these features.