Closure Mode for CoffeeScript
bolinfest.com
Closure Mode for CoffeeScript
1–10 of 20 posts
Re: Closure Mode for CoffeeScript
#2Re: Closure Mode for CoffeeScript
#3http://www.sitepoint.com/google-closure-how-not-to-write-jav...
Re: Closure Mode for CoffeeScript
#4@jashkenas -- any thoughts/concerns with this? How likely is it to hit main branch?
Re: Closure Mode for CoffeeScript
#5Google Closure: How Not to Write Javascript http://www.sitepoint.com/google-closure-how-not-to-write-jav...
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).
Re: Closure Mode for CoffeeScript
#6As a heavy user of Closure Compiler and a fan of CoffeeScript, I love love love the potential here. @jashkenas -- any thoughts/concerns with this? How likely is it to hit main branch?
Re: Closure Mode for CoffeeScript
#7As a heavy user of Closure Compiler and a fan of CoffeeScript, I love love love the potential here. @jashkenas -- any thoughts/concerns with this? How likely is it to hit main branch?
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.
Re: Closure Mode for CoffeeScript
#8Re: Closure Mode for CoffeeScript
#9Earlier quoted context omitted.
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.
It's an optional mode via command line, no? Opt-in won't require anyone to use closure.
Re: Closure Mode for CoffeeScript
#10Earlier quoted context omitted.
It's an optional mode via command line, no? Opt-in won't require anyone to use closure.
Fair enough ... it's definitely worth considering seriously. I'd probably wait until it's "finished" according to Michael, and then look at if it's possible to add enough hooks to the compiler for it to be implemented as a plugin. Ideally you'd be able to emit different annotations depending on your use case, for example: lots of other folks have requested automatic JSDoc annotations.