[calibraxis]

In my experience of using CoffeeScript, the author is absolutely correct. CoffeeScript is rejected for reasons "usually knee-jerk, or based on fallacies." I introduced it respectfully and fairly in a former team, and at first people are generally fainting and acting like the world will end.

(This is backend node.js work which emphasized tests and code review. I don't know what it's like outside that.)

Not all rejection is knee-jerk. "Usually" is the operative word here. I would have loved knowledgeable, reasoned critique. I personally assembled as many reasoned critiques as I could, to demonstrate my respect for reasoned, fair decisionmaking. I am continuously disappointed by the low standards of discourse, in programming culture.

(The first random misbegotten idea which pops into my lizard brain to confirm my prejudices, is not a sufficient "reason".)

Eventually, most realize CoffeeScript's sheer maintainability can far outweigh CoffeeScript's (real) flaws; some former detractors become downright zealots. Sure, some still dislike it; but they tend to be ignored because it's really not that bad. Nothing compared to the real problems that a team encounters.