Closure Mode for CoffeeScript (opens in new tab)

Not likely to hit the main branch, as it requires everyone who uses the language to also to use the Google Closure library, as well as the Closure compiler. But as a fork, I think it's brilliant.

When I met Jeremy at JSConf (this was at the end, during the super-loud party), I asked whether such a patch would ever be accepted, and he said, "no, probably not." Obviously that didn't stop me and I'm glad to hear that it would be considered once it has matured :)

If it were to happen, then yes, it should certainly be an option, though to clarify, you can use the Library without the Compiler, and the way things are written now, the only file from the Closure Library that your generated code would depend upon is the bootstrapping base.js file. (Though it may also depend on array.js down the road -- see the section "Leveraging More Closure Library Built-ins" on http://bolinfest.com/coffee/features.html.)

But I think it's completely fair to wait until it's "finished" before trying to upstream it, as Jeremy suggests. It will likely take a bit of refactoring for the CoffeeScript code to support "plugins" such as these. As you can see, I'm just spraying "if o.google" statements in https://github.com/bolinfest/coffee-script/blob/master/src/n... to get things done right now, which would not be acceptable to upstream in its current form.

I commented on this blog post a long time ago here on HN. So did many other HNer.

Whatever you might think about Closure, please do not make up your mind about it from this article. The author does not seem to be an experienced javascript developer (at that time).

Nobody uses that library anyways.

If you've been looking at the latest commits, effort is being done on adding type annotations to the Coffeescript grammar. Once these are completed, the resulting Javascript should be directly usable by the Compiler in advanced mode (to get the most optimized code with the Closure Compiler you will need type annotations for objects, function parameters and "typecasts"). I'm glad the effort is being focused on type annotations rather than Closure Library idioms (e.g. those under goog.array) at this stage. As someone who has to write lots of boilerplate code to leverage the power of Closure Library components I cannot thank this enough (and don't forget plovr!). Just the Coffeescript class declaration sugar that's working right now is quite powerful in terms of reduced noise in your code.

EDIT: wording.