The idea is intriguing. What if we think about tying a language to a library rather than the other way around? Lisp and Forth both had the idea that you should be able to build your language around the needs of your application, rather than the other way around, and this kind of source compilation feels like the extension of the idea.<p>(Yes, we could always do the same thing, and often have, but not in web-world.)
This is interesting, but tying a language to a particular (version of) a specific framework strikes me as a bad idea.<p>If the aim is to bake in syntactic sugar for different constructs within Ember that are awkward in plain CoffeeScript (and there are a few), wouldn't creating a CoffeeScript version of sweet.js[1] not be a better idea (I have no idea if such a thing exists already)?<p>[1] <a href="http://sweetjs.org/" rel="nofollow">http://sweetjs.org/</a>
I love the CoffeeScriptRedux project and this is a perfect little application of it. It's very easy to pick up once you know CoffeeScript and I love the idea of stylizing your developer tools to fit a framework as rightfully opinionated as Ember.