It's mildly annoying. Unlike Fortran, JS doesn't desperately need a preprocessor language. Adding another layer of "abstraction" and some syntactic sugar will make the process of developing good JS needlessly complex and fragile.
So "it turns out"[1] that Coffescript will make the process of developing good JS needlessly complex and fragile.
Would you care to elaborate?
From the coffeescript site :
> it compiles into clean JavaScript (the good parts) that can use existing JavaScript libraries seamlessly, and passes through JSLint without warnings. The compiled output is pretty-printed and quite readable.
When I used it, it cut ~25% of the LoC off my project. And it only took about an hour to learn because the documentation is so damn good. On the usefulness scale, I'd put it next to jQuery and backbone.js.
Comments
It's mildly annoying. Unlike Fortran, JS doesn't desperately need a preprocessor language. Adding another layer of "abstraction" and some syntactic sugar will make the process of developing good JS needlessly complex and fragile.
So "it turns out"[1] that Coffescript will make the process of developing good JS needlessly complex and fragile.
Would you care to elaborate?
From the coffeescript site :
> it compiles into clean JavaScript (the good parts) that can use existing JavaScript libraries seamlessly, and passes through JSLint without warnings. The compiled output is pretty-printed and quite readable.
[1]http://jsomers.net/blog/it-turns-out
When I used it, it cut ~25% of the LoC off my project. And it only took about an hour to learn because the documentation is so damn good. On the usefulness scale, I'd put it next to jQuery and backbone.js.