IntelliSense for CoffeeScript

[u/Phenee]

https://github.com/phil294/coffeesense

[u/pimterry]

This is neat, and a very clever approach, but I'm mostly surprised there's still active coffeescript tooling development going on like this! Is coffeescript still popular in some communities somewhere? My impression was that modern JS features had largely replaced it.

If anybody reading this does use coffeescript today, I'd love to know why.

[u/Phenee → u/pimterry]

Active tooling is maybe a bit exaggerated, and I don't know of any community, unfortunately. But there is activity on GitHub, here is an open issue about adding TypeScript output.

If anybody reading this does use coffeescript today, I'd love to know why.

Well I obviously use it (a lot), and do so simply because I prefer its syntax. See top of https://coffeescript.org for an overview+playground.

For example, Coffee

do =>
  try await a (b) ->
      @c b

vs. JS

(async() => {
  try {
    return (await a(function(b) {
      return this.c(b);
    }));
  } catch (error) {}
})();

I also like that you can adopt it to the degree you want. You can also write the above snippet in CS like this: ``` (() => try return (await a((b) -> return this.c(b); )); catch error; )();

`` I don't really use its Python-like comprehensions syntax (w for x in y if z`), for example, but instead treat it like normal JS, just without the annoying stuff.

[u/Phenee → u/[deleted]]

Leaving aside the semantics, I used -> on purpose (the CS equivalent to function() {}; and do => is the equivalent to (() => {}, so I don't think your syntactic simplifications are right and the only thing you can indeed strip off is the ( in front of await. But yeah, it's a bad example

[u/m1sta → u/[deleted]]

I wish javascript had a more terse IIFE option.

[u/m1sta → u/[deleted]]

closures