There are a few reasons we made the switch: - Familiarity. Most of our team have a little experience with Javascript, but none at all with CoffeeScript. It's n

There are a few reasons we made the switch: - Familiarity. Most of our team have a little experience with Javascript, but none at all with CoffeeScript. It's not that different, but there's still a cognitive overhead. - Documentation. Almost all documentation for front-end work, especially with React, is in ES6 now. There's an additional overhead in translating it. - React – CJSX was IMO awesome, but there's no ongoing support for it. Embedding JSX in CoffeeScript is less satisfactory. - Webpack. We've had various problems getting features of Webpack 2 to work correctly with pre-2.x CoffeeScript – HMR etc. that only really work with ES6 modules. We could wait for CoffeeScript 2, but it's already becoming a drag on velocity. In short, CoffeeScript was great, but the benefits are much more marginal now. My preference for terse syntax isn't that high a priority for the rest of my team, so I'm happy to take advantage of the more standard ES6 that we can now use.