<story><title>IcedCoffeeScript</title><url>http://maxtaco.github.com/coffee-script/</url><text></text></story><parent_chain></parent_chain><comment><author>swannodette</author><text>This fork brings some up deep issues, perhaps intractable, around
about the development of syntax-y languages. Useful source
transformations require marginalized forks of the compiler and all the
development burden and risks that entails. In some sense CoffeeScript
inherits the &lt;i&gt;actual problem&lt;/i&gt; with JavaScript - a select few determine
the introduction of language features. Perhaps these language
features are best shipped as libraries?&lt;p&gt;Maybe it doesn&apos;t matter. Perhaps most users don&apos;t need it. Or perhaps
as we continue to develop software we&apos;ll find that we&apos;d rather defer work to the
compiler / macros and the high cost of syntax is simply not worth it.&lt;p&gt;I&apos;m looking forward to see how 3 languages I immensely enjoy (JavaScript, CoffeeScript, ClojureScript) co-evolve :)</text></comment>
<story><title>IcedCoffeeScript</title><url>http://maxtaco.github.com/coffee-script/</url><text></text></story><parent_chain></parent_chain><comment><author>mayoff</author><text>I was going to complain that I could find no mention of TameJS (from which the await and defer keywords/features clearly originated).  Then I noticed that the IcedCoffeeScript author is also the author of TameJS.</text></comment>