Comments

  1. Wednesday, June 10, 2015 10:40:02 PM by Peej
    This is interesting, would you recommend a startup look at closure from the getgo or do you think it is more a solution for large scale applications?
  2. Thursday, June 11, 2015 6:12:49 AM by Manole
    I never would have thought in 2015 people still using this pile of shit...
  3. Thursday, June 11, 2015 8:24:05 AM by skrat
    Thanks for wrapping it up. GC is still the best JS2JS compiler around, no one else was able to put up so much effort. @Manole looking for a pile of shit? Head to npmjs.org
  4. Friday, June 12, 2015 9:55:14 AM by monzonj
    I love the closure tools. I just wish getting started was easier (the tooling is dreadful) and that it worked with nodeJS build tools like gulp and grunt (doesn't support piping, and it's kind of a pain because of the JVM).

    Some common tasks like using modules and dependency resolution could be handle way better (do we really need to run all those python scripts?)

    Using angular or any other JS framework isn't incompatible with the closure tools. Actually there are annotations and helpers that makes closure and angular perfect companions.

    I'm moving away from closure to bable. Arguably a much better EMACSCRIPT2015 to EMACSCRIPT3 than closure compiler, better to get started with and better support.
  5. Friday, June 12, 2015 10:07:08 AM by Daniel Szmulewicz
    Figwheel, yes, but also interactive programming with Boot and system.
    https://github.com/danielsz/holygrail
  6. Saturday, October 10, 2015 12:53:17 AM by Paul
    After having adopted Closure in my own work, I'm shocked at how little adoption there has been. It does take a while to get going, but once you do, there's nothing like it. Even in 2015.
  7. Tuesday, October 27, 2015 6:55:23 PM by J. M.
    This is a well-written article. The author understands what Closure Library and Compiler bring to the table. Concepts like dead code elimination are massive wins to anyone who's serious about creating scalable/browser-compatible JS.

    As others have said, the ramp up can be hard, but the Closure team is working on this. File bugs on the github project (https://github.com/google/closure-library) if you have ideas for making the introduction easier or improving tooling.
  8. Monday, November 23, 2015 9:28:09 PM by JD
    I did use google closure for our work in company . The kind of support for compiler , Closure templates and Also in UI , component and control classes .But only drawback it did not played well with other JS framework.



    It is very sad to see , so few people adopted google closure.
Add Comment