| The example given is valid js... Nobody is "force-feeding" you anything, just close your browser tab. If you missed the top of the article, it's the author that was offended first for using CS, there's no need to continue calling names. And please drop the straw man arguments: > 1. In order to debug CoffeeScript, I will need to know JavaScript. Of course, and that's the beauty of it. CoffeeScript is a tool to write javascript. > 2. If I run into a tricky problem, not only will I need to know JavaScript but I'll also need to know the CoffeeScript compiler's internals. You never have to know the CS compiler's internals. The output is always valid (if it wasn't that would be a serious bug, not a problem in your script). > 3. If I run into a really tricky problem, or if I need some sort of optimization, I might have to use JavaScript anyway. Optimization can be done in CoffeeScript itself 99% of the times, and it already outputs very efficient javascript. > 5. All of the libraries I will be using will be written in JavaScript. Yes, that's nice isn't it? They all interact perfectly fine with your CS code. |