Comments

  1. Monday, June 28, 2010 10:32:01 PM by Martin S.
    I'm behind http://letsannotate.com - collaborative document review.

    We use GWT instead of Closure. When we started developing Closure was freshly released and since it's used in Google Docs, Gmail, etc. we were strongly considering it.

    In the end there were a few features in GWT that made it worth to write Java instead of Javascript:

    * UiBinder (http://code.google.com/p/google-web-toolkit/wiki/UiBinder) Which is Templating + CSS Sprites + much more

    * Deferred Binding (http://code.google.com/webtoolkit/doc/1.6/FAQ_Client.html#What_is_Deferred_Binding?) GWT automatically compiles multiple .js files, each for a different browser/locale combination. It's extremly easy to add another parameter to it, like - in our case - iPad support. If you visit letsannotate.com on your iPad we switch out the View Classes to provide a touch optimized experience.
    AFAIK Closure has no equivalent to deferred binding

    * MVP architecture: When we were evaluating GWT vs. Closure it became clear that Patterns and Best Practices for developing large applications are much more readily available for GWT than for Closure. (e.g. http://code.google.com/events/io/2009/sessions/GoogleWebToolkitBestPractices.html)
    While Closure was used to write GMail, there seems to be no agreed upon best practice for navigation, MVP separation and so on. This is where GWT shines the most. It's incredibly easy to architect an application that's capable of growth, simply because Google tells you how to do it. While the API reference for Closure Library is comprehensive, I didn't find any such documentation.

    All in all I'd currently recommed GWT for Web App development over Closure, but that might change in a year or two if Google (or someone else) releases similiar best practice code for Closure.
  2. Tuesday, June 29, 2010 7:42:37 AM by markvgti
    Thanks for taking the time to write this. There is too little material related to Google's Closure tools available online — every little bit helps (and this is a good introduction).

    I use a lot of Google libraries/APIs, and even I didn't know about Closure Tools till I noticed a presentation on it at the recent Google I/O 2010 conference.
  3. Wednesday, February 22, 2012 7:00:23 PM by Web Developer
    Thanks for a great introduction of Google Closure tool. Yes, it's an overkill for light applications. I prefer jquery over Google Closure.
  4. Sunday, March 25, 2012 8:19:42 AM by Dave Fisher
    Closure is pretty easy to use, but I run into situations all the time where I need to need to compile again just to make a small change. I get annoyed by that (for example with Chrome Extensions). Overall I find the framework very easy to use. Once you find an example Ant build file for closure builder. :)
  5. Saturday, July 28, 2012 1:19:29 PM by Shripad K
    @Dave Fisher: use plovr. no need for ant build files. plovr is plain awesome.
  6. Sunday, October 14, 2012 4:43:57 PM by Ken McGelt
    Excellent! Just what I needed. Thanks!!
  7. Thursday, January 24, 2013 5:10:10 AM by Roseindia
    Hi,

    The Google Closure tools is one of the best tools that helps programmers/developers to make web applications using this Google Clousure tools. This clousure tools was developed by Google developers for using this tool in their web applications like gmail, google docs and google maps and many more.
  8. Friday, March 29, 2013 1:12:32 PM by Billboardflex
    I am really very impress with this post. I will it with my programmer friends.

    Hope you will share more useful post as this in future too.

    Thanks
  9. Saturday, April 06, 2013 5:59:29 AM by Google
    Google is Great. Read more about Google.
  10. Friday, November 01, 2013 9:39:41 AM by ku-isi blog
    thanks great Good
Add Comment