The author says they contemplated an “abandon this ruined planet” option, mentioning Haxe/Clojure/Elm as alternatives. I'd love to read their follow-up post to

The author says they contemplated an “abandon this ruined planet” option, mentioning Haxe/Clojure/Elm as alternatives. I'd love to read their follow-up post to learn what kept them on planet JavaScript/TypeScript. The alternatives to TypeScript seem increasingly compelling to me. It was good to see Haxe mentioned even in passing; I really enjoy using it and — as others have noted[1] — it feels like a “better” TypeScript. Haxe has great features both at the language-level (pattern matching, algebraic data types, array comprehensions, and more[2]) and tooling-level (cross-compilation to JavaScript, native code and dynamic languages, a fast compilation server[3], good VS Code support in Haxe 4, and a bunch of cross-platform game frameworks[4]). I wish more people would try it! https://haxe.org/ https://haxe.org/ Reason is also compelling; it will be better still once Bucklescript's Belt library is out of beta and some warts in Reason/OCaml are smoothed out — lack of ad-hoc polymorphism[5] and lack of unicode support without BuckleScript string literals being two examples. [1]: https://news.ycombinator.com/item?id=10009290 https://news.ycombinator.com/item?id=10009290 [2]: https://haxe.org/documentation/introduction/language-features.html https://haxe.org/documentation/introduction/language-feature... [3]: https://haxe.org/blog/nicolas-about-haxe-episode-1/ https://haxe.org/blog/nicolas-about-haxe-episode-1/ [4]: https://haxe.org/use-cases/games/ https://haxe.org/use-cases/games/ [5]: http://ocamllabs.io/doc/implicits.html http://ocamllabs.io/doc/implicits.html