Elm vs. PureScript
gist.github.com
gist.github.com
I don't think so.
Elm is too much in its own world.
Purescript is too Haskell for mainstream.
I had the impression that Reason/ReScript was on a good way, but the I think the renaming and split of ReScript from Reason confused people, and now nobody knows what's happening anymore. (Im still confused myself, haha)
Maybe Rust has a chance in the frontend world if it gets just a bit more ergonomic?
Also I don't know why these languages aren't being promoted more for backend development as it's a perfect fit for the paradigms espoused in https://pragprog.com/titles/swdddf/domain-modeling-made-func.... I would say Ocaml/ReasonML is even more ergonomic than F# (polymorphic variants are great for composable error handling).
Even in the current state, ReasonML can be used to progressively enhance a JS or even typescript codebase with no need to fully buy into a rewrite or even heavy toolchain modifications.
It is?! I thought I was following the changes there - clearly I was mistaken
Elm, Purescript, and Reason will likely all remain niche, or die off. Some developers will springboard from Typescript into these languages (but probably not Elm, sadly I think it's doomed, and not for being a bad language) but most people will I think be fairly content.
Perhaps something will come out of leftfield, but I can't see something like Rust-with-better-ergonomics taking that much mindshare from Typescript. A JS dev can start with Typescript today, in their existing codebase, and be productive either immediately, or within a few days. It's pretty hard to beat that, though I'm sure there will be niches for the various other compile-to-JS or compile-to-WASM options.
I don't think Rust has the right trade-offs to make it a good choice today, but I expect that to change.