This is not the first article talking about CoffeeScript's ambiguity and readability issues. It's interesting how CoffeeScript fans almost always decide to bla

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 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.