3 ms·

I personally skipped Coffescript, Javascript Generators and Angular. And none of them passed the test of time. So I think I made the right call by not adoptin

I personally skipped Coffescript, Javascript Generators and Angular. And none of them passed the test of time. So I think I made the right call by not adopting them super early. I think I'm going to do the same with Typescript. Hopefully static typing will be adopted by ES.Next and then I'll port my programs to it.

nine_k 9y ago
I wonder what are the chances of Typescript becoming (part of) ES.Next. It joins with plain JS as seamlessly as possible.
- tycho01 9y ago
  See this thread: https://esdiscuss.org/topic/es8-proposal-optional-static-typing https://esdiscuss.org/topic/es8-proposal-optional-static-typ... Note that things have moved a bit, and we're now only a few standing proposals away from being able to properly infer the challenging functions mentioned there.
johnfn 9y ago
Er, JS generators definitely did pass the test of time and are now part of modern JS.
- dvlsg 9y ago
  In fact, they are how async / await is implemented.
- 18nleung 9y ago
  With async/await there's not much of a case for their use anymore, though
  - AgentME 9y ago
    The regular generator use (return a lazily-evaluated iterator) still exists.