7 ms·

I'm pledging $1,000 to this. As the author of the PragProg book on CoffeeScript (http://pragprog.com/book/tbcoffee/coffeescript http://pragprog.com/book/tbcoffe

I'm pledging $1,000 to this. As the author of the PragProg book on CoffeeScript (http://pragprog.com/book/tbcoffee/coffeescript http://pragprog.com/book/tbcoffee/coffeescript), I have a stake in making CoffeeScript a more mainstream tool, and I believe that Michael's project will greatly advance this cause. The use of CoffeeScript has become fairly widespread at startups (GitHub, 37signals, many YC alums...) but not in larger enterprises. One reason for this is that debugging CoffeeScript requires a "hacker mentality": compile-time errors are often reported with minimal or misleading explanations (e.g. "Unexpected ," when there is no comma on the line, but rather an implicit comma from whitespace); run-time errors have to be manually traced from the compiled JS to the original CoffeeScript. These flaws are likely to be ameliorated gradually (Jeremy has stated that Source Map support is the primary goal for CoffeeScript 1.4), but this project could improve the debugging situation dramatically in a matter of months. I hope the CoffeeScript community will lend Michael their support.

flywheel 14y ago
You're spending so much effort to distance yourself from javascript, when javascript isn't difficult, and coffeescript doesn't solve many problems while introducing its own problems. You must be a masochist if you support coffeescript so much and just refuse to code javascript. It's just such a backwards way to develop. Coffeescript is not becoming "widespread", and it doesn't require a "hacker mentality", it is simply a syntax fetish that dithers modern web development. It is a "made-up" language that has been way over-hyped to the point that people start believing that it's a good thing to stick yet another abstraction layer between the DOM and the code. Updates to coffeescript have broken existing code, how is this a good thing? Good luck with that.

flywheel 14y ago

You're spending so much effort to distance yourself from javascript, when javascript isn't difficult, and coffeescript doesn't solve many problems while introducing its own problems. You must be a masochist if you support coffeescript so much and just refuse to code javascript. It's just such a backwards way to develop. Coffeescript is not becoming "widespread", and it doesn't require a "hacker mentality", it is simply a syntax fetish that dithers modern web development. It is a "made-up" language that has been way over-hyped to the point that people start believing that it's a good thing to stick yet another abstraction layer between the DOM and the code. Updates to coffeescript have broken existing code, how is this a good thing? Good luck with that.