I mean, look at what Hello World in C is, compared to Hello World in Haskell!
http://pastebin.com/sePpUJ1J (Haskell source)
http://pastebin.com/seqAy4VD (C, generated from the Haskell above)
Clearly C is unreadable garbage! (It's less expressive than Haskell, for sure, but showing generated output makes it look far worse)
This makes CoffeeScript fit really well into the JS-centric environment that has grown up around tools like JQuery and backbone. It's also very easy to debug in the browser compared to the environments that are targeting JS as an object code.
Personally, I don't think of CoffeeScript as a fully independent language but, rather, as a way to write JS which is cleaner, more reliable, and more fun.
If you really want to turn JS into a black box (and there are some good arguments for that), GWT or ClojureScript might be better choices for you.
(I've been writing a bunch of CoffeeScript lately and loving it. I'm very anxious to try my hand at ClojureScript also. GWT has always seemed very unwieldy to me.)
Dear sir,
I'm jumping on my bed right now out of ecstasy, for my unworthy comment has garnered a reception, from a noble soul like yours.
You just made by day. In fact, you do it through the means of coffeescript everyday. Thank you for coffeescript, kind sir.
Hats off.
A broke, insecure, forever alone developer.
</public_display_of_affection>
... which does indeed miss the point -- the side-by-side comparison on the homepage is not to show you what the equivalent handwritten JavaScript would be -- it's the actual JS output compiled from the CoffeeScript on the left. More of a "nothing up my sleeves" and no bullshit maneuver.
In a perfect world, CoffeeScript would compile into the JavaScript you would have written in the first place -- but that's quite a tall order.