What is the maintenance burden of the average React app? When I have written an Elm app, I feel confident that I could come back to it in a few years time with no issues.
To me, this stability is a testament to the language's thoughtful design and rejection of the constant churn of contemporary web development. At the risk of sounding like a Game of Thrones fan waiting for Winds of Winter, I look forward to the next version coming out with modest changes and bug fixes whenever it is ready.
It is clear that Elm is understaffed, to say the least.
Live projects appear to be alive. There is activity, developers to talk to, support to purchase, release notes to read, even if those release notes are just maintenance notes for mature software. If your evidence of life is pointing to a two year old forum comment, I hate to break it to you, it's dead.
It's impossible to evangelise something when the creator has seemingly taken his ball and gone home.
The idea that enterprise should use Elm is laughable.
Edit: moved the position of the citation.
https://discourse.elm-lang.org/t/is-elm-browser-still-mainta...
https://discourse.elm-lang.org/t/request-elm-0-19-2-any-upda...
It's pretty sad. I personally believe the ecosystem would be in a much more vibrant state today, if the creator had formally abandoned the language at any point in the past, as there are many who would pick up the torch.
It is telling that several people who could once have been considered 'core team' are now building their own languages: