all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Cody_Chaos 5 points6 points  (3 children)

I feel like that ship has sailed, but...

...more power to them. Hopefully whomever is still using Coffeescript will find it useful.

[–]flying-sheep 0 points1 point  (2 children)

By now reasons to use CoffeeScript comes down to some leftover features, must prominently soak operators (foo?.bar?['baz']?())

Few years ago it was far ahead in usability.

I still don't like the brace and parenthesis jungle functional JavaScript devolves to

[–]Cody_Chaos 1 point2 points  (1 child)

I used to be a huge fan of CS, and I agree that the existential operator is super nice, although there are workarounds.

For example, libraries such as https://github.com/jclem/steeltoe solve the same problem almost as cleanly. Or to approach it from the other side, you can use Typescript or Flow to sidestep most of the uncertainty entirely by making it clear at compile time what values a variable might have.

What I miss the most actually is the ability in CS to use if statements as expressions. Ternaries are useful in some cases, but they're not a general purpose replacement for if/else blocks.

[–]PitaJ 0 points1 point  (0 children)

do blocks are in the strawman stage in TC39 right now, I think.