3 ms·
And what's the lost efficiency for hitting into incompatibilities between JS<>Coffescript, like the topic? JS seems small enough that you shouldn't have many p
by raverbashing 12y ago
And what's the lost efficiency for hitting into incompatibilities between JS<>Coffescript, like the topic?
JS seems small enough that you shouldn't have many problems in this matter, but there's usually some warts
- conanbatt 12y agoThere is a cost, but its without a doubt heavily outbalanced by having half the code. The JS it generates is a tad ugly, but you save way more time, clarity and readability than with vanilla JS.
- skilesare 12y agoThis is the first issue like this that I've seen. I actually didn't know about that particular syntax. I've been doing @example inside my code when I need 'this'. Coffeescript is just coffeescript so there really aren't any incompatibilities. The only gotcha that I've hit a few times was the automatic returns that are inserted. Sometimes you have a chain of functions that requires a true to be returned from a function and if you don't do it explicitly, coffeescript will return a falsy value.