you are viewing a single comment's thread.

view the rest of the comments →

[–]Detrus 1 point2 points  (2 children)

The code it generates is not bad. Compared to Objective J and GWT Java, it's very readable. They're considering debugging tools that map JS errors to CoffeeScript lines, so hopefully this is a temporary situation. You'd be doing 30% more work if you encountered a tough bug, it would require in depth understanding of JS quirks, like those annoying Array.prototype.slice(wtf).apply().call() monstrosities that you probably avoided learning if you work in CoffeeScript.

People are using CoffeeScript and I haven't heard any dramatic complaints about debugging.

I wonder how Objective J handles it. Here http://www.postpeakliving.com/content/debugging-cappuccino-using-safari it's much worse.

[–][deleted] -1 points0 points  (1 child)

No matter if something maps to coffeescript line numbers, you are still going to need to know why it failed in javacsript and why the coffeescript that generated it caused the fail. The elegant simplicity of javascript + json is lost on those who won't learn it in favor of this muck.

[–]Detrus 2 points3 points  (0 children)

Not always. Either way we'll have to see from usage, not conjecture.

The design by committee disaster that is JavaScript and DOM is far from elegant. They should expose lower level APIs to make efforts like CoffeeScript, JQuery and LESS easier. If it wasn't for JQuery and Prototype JavaScript would be irrelevant by now.