This article screams of:
"I dont want to learn CoffeeScript, Don't use it!"
His basis of not having to learn CoffeeScript is that he uses structural js frameworks? Like somehow CoffeeScript prevents you from doing that?
I'm all for sound reasoning showing pitfalls of certain languages - which despite its wordiness, the article demonstrates a severe lack of. IMO the biggest reason not to use CoffeeScript is the lack of a good debugging experience. Although that's about to get better with soon being able to write source debug symbols in js for transpiled languages.
At the same time the JavaScript language is constantly improving (albeit slowly), which ideally would mitigate the need for CoffeeScript / Dart / etc. But that's not going to be available in mainstream client js programming for years to come. In the meantime feel free to use what language you feel more productive in - and stop trying to impose your personal taste onto others.
His basis of not having to learn CoffeeScript is that he uses structural js frameworks? Like somehow CoffeeScript prevents you from doing that?
I'm all for sound reasoning showing pitfalls of certain languages - which despite its wordiness, the article demonstrates a severe lack of. IMO the biggest reason not to use CoffeeScript is the lack of a good debugging experience. Although that's about to get better with soon being able to write source debug symbols in js for transpiled languages.
At the same time the JavaScript language is constantly improving (albeit slowly), which ideally would mitigate the need for CoffeeScript / Dart / etc. But that's not going to be available in mainstream client js programming for years to come. In the meantime feel free to use what language you feel more productive in - and stop trying to impose your personal taste onto others.