3 ms·
I'm glad to see you agree. I haven't had time to evaluate CoffeeScript, and now I don't need to make it because the advantages CoffeScript offers are not issues
by michaelwww 14y ago
I'm glad to see you agree. I haven't had time to evaluate CoffeeScript, and now I don't need to make it because the advantages CoffeScript offers are not issues that bother me and it introduces issues that would bother me.
- tlrobinson 14y agoI wouldn't dismiss it so quickly. I dabbled with CoffeeScript for awhile, but didn't enjoy it until I used it full time for a week or two, and now I can't go back to JavaScript. The issues brought up in the article are annoying, but no more so than JavaScript's own annoyances (and in fact CoffeeScript fixes some of JavaScript's annoyances). After a couple weeks of using it you'll know what to watch out for an it will be very pleasant to use.
- betterimposter 14y agoYea, but the write-up failed to mention a few of the other advantages, most notably, comprehensions. Every time I do a for, map, filter, etc. in js, I wish I was writing coffee. Having said that, if the verbosity of array ops aren't a sticking point, then I say don't bother. I'd probably be just fine with js if I'd never typed dog.praise() for dog in dogs when dog.type is 'pet' I have gotten into the habit of singing these, so its probably just an oddity I have. Carry on and ignore.
- michaelwww 14y agoTo each his own. I quite happy with C-like languages with braces for blocks.