3 ms·

I respect CoffeeScript for what it did and playing a part in making Javascript and its ecosystem better. That said, for a new development, is there any reason

• anythrow123 9y ago
  > an upgrade target for existing codebases That might be a little naive. I pick Coffeescript in a reflex without even considering ESxx, and I regularly start new projects large and small with it that go into production. It's a breeze compared to some of the modern Javascript codebases I have to work on. My overall development speed is definitely faster in Coffeescript, less bugs, no countless babel add-ons, no linters etc.. and the codebase often speaks for itself, less annotations, less code. Efficiency means a lot to me.
• molszanski 9y ago
  > That said, for a new development, is there any reason to use it over ES6? Obviously your mileage may wary. I think, the biggest reason is a time boost. - Less noisy code (no braces etc) that is easier to scan - No time wasted on flirting with new ESXXXy stuff - There is no callback hell to deal with - Writing React code is sweet. As previously noted: http://rapin.com/blog/2015/02/03/reactjs-with-coffeescript/ http://rapin.com/blog/2015/02/03/reactjs-with-coffeescript/ - Less distractions on things that don't really matter in 98% of use cases. Like var/const/let declarations
  • cos_ 9y ago
    + very lightweight dependency to pull in, in contrast to installing the operatingsystem-size babel (tip: there´s also buble)