3 ms·
At the risk of hijacking the comment thread for an article about NodeJS to grandstand about CoffeeScript: I'm not a big fan of leaky abstractions, and right no
by spjwebster 15y ago
At the risk of hijacking the comment thread for an article about NodeJS to grandstand about CoffeeScript:
I'm not a big fan of leaky abstractions, and right now that's what CoffeeScript is. It will be somewhat less leaky once this has been resolved:
https://bugzilla.mozilla.org/show_bug.cgi?id=618650 https://bugzilla.mozilla.org/show_bug.cgi?id=618650
…for all browsers.
I'm happy for CoffeeScript to exist, to be able to play with it, and to see its syntax inform the work on JS.next. It has a way to go before I'd be happy to use it in a production environment.
- wisty 15y agoCoffeeScript creates very readable JS code. I haven't seen it do much funky stuff. It mostly just adds ";" after statements, and gets rid of the "variables are local unless you * explicitly* declare them local" thing, and so on.
- ehsanu1 15y agoWhile this is an issue, it's a pretty minor one from my own (limited) experience using CoffeeScript. It's extremely easy to relate the JS errors to your CS code, since the JS generated is so readable. It's just a little tedious to have to take a look at the generated JS, but not that bad really. Try it out for some node.js stuff and see for yourself. Also, the issue is being fixed for Chrome/Firefox, which is good enough for dev work.