> Elm gets plundered repeatedly before it ever reaches version 1.0.

I concur. Ever since Elm 0.17 [1], when Evan removed event streams and standardized on The Elm Architecture, Elm seems to have lost its way. Just saying as an interested outsider.

[1] https://elm-lang.org/blog/farewell-to-frp

I presume it is a matter of perception: Elm is now perceived as a GUI toolkit rather than a language in its own right. Elm achieved simplicity and, ironically because of that, it is now plain easy to port its main ideas to other languages.

Because elm is elegant. I have written web-app with elm on the client side and rust in the backend. It was great, except for duplication of code when serializing/deserializing json data when making API calls. With sauron, I save up a lot of duplicated codes, and gotta squeeze that webassembly performance as well.

The main issue with Elm is the glacial development pace. I understand why it is the way it is (it shows in how well designed what is there is), but it really does hurt as someone who wants to adopt it.

Yep! I'm writing this from Elm in the Spring, the 2nd of 4 dedicated Elm conferences in 2019.

JS/TS continue to dwarf everything else, but it's possible that Elm is the most widely used JS alternative at this point. (Hard to know definitely though!)

I like to think Elm is the most influential web framework that no-one uses.

We're using Elm for our front-end UI. With Erlang in the backend (not Elixir). It's very reliable and predictable. I hope it succeeds.