Why I'll (probably) never use CoffeeScript

Dustin Byrne beschreibt in diesem Artikel ganz gut wo der Schuh, bei der Entwicklung mit CoffeeScript, drückt. Der Fairness halber sei angemerkt, dass die Browserhersteller wohl an Lösungen arbeiten.

If I write my client-side code in CoffeeScript, the browser still receives and runs Javascript. That creates a huge disconnect between what I’m writing and what I’m running. Now maybe your code runs perfectly every time, but mine doesn’t. And when it doesn’t, I look at what’s happening in the debugger. What do I see in the debugger if I use CoffeeScript? Not my code, but a derivative of my code. What do I have to do to fix a bug? Mentally decompile the running Javascript to the source CoffeeScript, make the change in the CoffeeScript, and hope that it compiles back down to the Javascript that fixes my problem. Harsh.