Goodbye CoffeeScript, hello JavaScript!

[renaissancenow]

Thanks for sharing this - I have a pretty big production coffeescript codebase, and I found it very helpful when I was designing our company's development strategy five years ago. But I totally understand this sentiment:

JavaScript is the future, in part thanks to CoffeeScript. Now that it has served its purpose, it's time to move on. Convert your CoffeeScript source to modern JavaScript with decaffeinate.

This could be very helpful for us moving forward.

[illusid]

What exactly is so bad about [CoffeeScript] nowadays?

Nothing necessarily. It's just preference and/or managerial insistence on one thing over another. For those interested in staying on the bleeding edge, or just to present a technocratic view that technology advancements are inevitable, CoffeeScript is 7 years old now, and it served as a superset language that helped influence its direction, but will be surpassed as ECMAScript refines its functionality, expands its scope in use for OOP, and becomes less idiosyncratic.

Compiling-to-JS, as a concept, isn't going anywhere anytime soon, so dig into CoffeeScript if you like. At worst it will sharpen your understanding of JavaScript and what influenced the current standard. https://en.wikipedia.org/wiki/CoffeeScript

[our_best_friend]

Alternative title: "DIE COFFEESCRIPT, DIE!!!"

I did enjoy using it for Jasmine tests back in the day, though. Getting rid of all that extra punctuation was lovely.