Hacker News new | ask | show | jobs
by pestaa 5175 days ago
Fully agreed. The syntactic sugar saves lots of time in total, and there are few bonuses like

    for own key, value in hash
that also checks `hash.hasOwnProperty(key)`, which is good practice in JavaScript, but really boring to type in almost all `for` statements.

I also observed that using longer, more descriptive variable and function names, the difference between Coffee and compiled JS is definitely not an issue in debugging sessions. I'd say there is not a context switch even.

It feels like thinking in JavaScript and writing in a new dialect.

1 comments

> but really boring to type in almost all `for` statements.

Use _.each, you're done. Pleasure.

Except that if you're, say, performing nested iteration, you end up creating a whole crapload of closures, ballooning up memory usage and punishing the GC.

A quick test show that coffeescript's iterator is about three times faster. http://pastie.org/3783184

Underscore's nice, but I really like Coffeescript's iterator sugar.

But performance