It's Typescript for the immediate future. It's where the resources are (Microsoft, etc), it's where the type definitions are for the libraries you want to use (

It's Typescript for the immediate future. It's where the resources are (Microsoft, etc), it's where the type definitions are for the libraries you want to use (don't underestimate this one!), and it's where the developers and jobs are. For a lot of people it's a big enough step up over JS (while still being very familiar) that it's more than good enough. 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.