The problem with Coffeescript: debugging
To keep it short, you can write your so called "elegant" coffeescript, but when it comes down to debugging the output it's going to be JS. JS _you_ didn't write.
So yeah, it's a sophomoric exercise that only adds complexity to building software. Obviously this is the #1 thing that should be avoided (unnecessary complexity) in all software. Adding more complexity is why developers _should_ get fired.
edit: Suggestions adding extra complexity to the development lifecycle do not make a case for coffeescript. They only make a case against it. That includes having to learn a useless language.
15 comments
[ 4.5 ms ] story [ 46.9 ms ] thread2. the generated js isn't that complex and you can easily map it in your head- it's not like trying to "debug" asm generated from C.
3. you'll get debugging soon (as wmf said, source maps- now waiting for cs guys to support in chrome, Rubymine IDE supports in D1 2013)
4. productivity is important.
"All code has bugs" claim is true, but it doesn't mean you need debuggers in order to solve/fix the problems.
If your methods ARE small enough, and you have tests for OTHER cases, printing/console is actually faster (at least for me) than using a debugger. I have a JS debugger in firebug, and I rarely use it (for pure JS, not just CoffeeScript output).
As long as you're glad with your false assumptions, I have nothing more to add.
You may not think this is an important point, but that doesn't mean that people who actually understand software development do.
See, even those who use it can't actually make a real argument against this other than it was easy for them. Whatever that means ... https://tech.dropbox.com/?p=361