The author keeps mentioning typos, it sounds like they should be using something with more checking and type safety that compiles to javascript, such as Dart, Typescript or Flow. That is what I would use if I wanted to write javascript (I program in C++).
I hate articles that say “Don’t you just hate this problem, blah, blah, blah, it’s the end of the world, blah, we’re all going to die, blah, blah, that’s why you should use product x which I happen to be the founder of”.
A good unintentional argument for having at least some concept of a monad in your language design, so that these constructs don’t have be keywords (or that, when you do introduce these concepts, you don’t bamboozle your users with keywords and ‘CSP’ and trivialities). Modulo Haskell, F#’s computed expressions seem to be the only bright light in this area. One of the benefits of having a massive programming-languages R&D department, I suppose :)
The author keeps mentioning typos, it sounds like they should be using something with more checking and type safety that compiles to javascript, such as Dart, Typescript or Flow. That is what I would use if I wanted to write javascript (I program in C++).
I hate articles that say “Don’t you just hate this problem, blah, blah, blah, it’s the end of the world, blah, we’re all going to die, blah, blah, that’s why you should use product x which I happen to be the founder of”.
A good unintentional argument for having at least some concept of a monad in your language design, so that these constructs don’t have be keywords (or that, when you do introduce these concepts, you don’t bamboozle your users with keywords and ‘CSP’ and trivialities). Modulo Haskell, F#’s computed expressions seem to be the only bright light in this area. One of the benefits of having a massive programming-languages R&D department, I suppose :)