I recently migrated a fairly large CoffeeScript project to JS, after using CS for more than three years. ES6 and ES7 addresses many of the pain points of JS right now. So my sugggestion would be to use an ES6/ES7 transpiler instead of CoffeeScript.
- JS produced by the CS compiler isn't that great, to be honest.
- Plain JS is easier to debug than CS, even though you have source maps.
- Source map chains don't always work. So using CoffeeScript together with another tool which produces its own source maps could be a problem.
- Build time could go down without CS
- Way more devs understand JS than CS
- I might have considered sticking with CoffeeScript if it had plans to evolve, perhaps add more functional features. But jashkenas considers CoffeeScript mostly done. As michaelficarra mentions in https://github.com/jashkenas/coffeescript/issues/3073, "CoffeeScript needs to evolve or die"
- When ES6 gets implemented, just get rid of the ES6/ES7 transpiler and you have plain JS
I haven't read the article, but if you ask me CoffeeScript is dying.
- JS produced by the CS compiler isn't that great, to be honest.
- Plain JS is easier to debug than CS, even though you have source maps.
- Source map chains don't always work. So using CoffeeScript together with another tool which produces its own source maps could be a problem.
- Build time could go down without CS
- Way more devs understand JS than CS
- I might have considered sticking with CoffeeScript if it had plans to evolve, perhaps add more functional features. But jashkenas considers CoffeeScript mostly done. As michaelficarra mentions in https://github.com/jashkenas/coffeescript/issues/3073, "CoffeeScript needs to evolve or die"
- When ES6 gets implemented, just get rid of the ES6/ES7 transpiler and you have plain JS
I haven't read the article, but if you ask me CoffeeScript is dying.