News for hackers. Stuff that matters.
Re:Why CoffeeScript Isn't the Answer by ceronman on Sunday March 30, 2014 @05:12PM (#7497955)
This is not the first article talking about CoffeeScript's ambiguity and readability issues.

It's interesting how CoffeeScript fans almost always decide to blame the programmers for these problems. They said good developers should use common sense and use best practices to make code readable, for example by always using parentheses when calling functions. I hear exactly the same argument in the Perl community.

But reality is that if a language allows you to write bad code easily, people will write bad code, and you will have to read bad code. This is very easy to verify: most CS project on GitHub, starting with the CS code itself (http://github.com/jashkenas/coffee-script) contain a lot of bad ambuigous uses of the language. A very similar thing happens with Perl code.

Programming language design is not only about making it easy to write good code, but also about making it hard to write bad one.

Re:Why CoffeeScript Isn't the Answer by nebstrebor on Sunday March 30, 2014 @10:34PM (#7499219)
It is hard to argue, however, that Javascript (the thing Cofeescript purports to improve) doesn't "allow you to write bad code easily" or "makes it hard to write bad code". I have avoided Coffeescript and probably will continue to do so, but it seems to at least try to make it a bit harder to write bad code, albeit not getting all the way there apparently.