1. 19
  1.  

  2. 4

    It’s interesting that they’re still working on CoffeeScript. The last time I used it was back in 2012 I think. I started using it while I was at ESPN and brought it over to Nickelodeon briefly before we went back to plain vanilla JS.

    With ES6, there’s not much reason to use CoffeeScript for me. I’m happy for what they ended up getting into ES6, though.

    1. 4

      That was sort of my takeaway when seeing this. Maybe I’m missing something, but why would I use CoffeeScript 2 when ES6 is becoming more and more popular? The only good reason I can think of is if I had deep reliance on CoffeeScript 1 and this fixed a bunch of issues.

      1. 1

        Yeah, you’d have to be heavily invested in CoffeeScript to be using it at this point, IMO. If you’re starting fresh, it doesn’t really provide any advantages over ES6, especially since it compiles down to ES6 now anyway. You’re still going to be doing transpiling when necessary.

      2. 1

        Yeah; I think it’s telling that their comparison of CoffeeScript to JS is still showing ES5. If they showed ES6, it’d be visibly less compelling than it used to be.