I don't think so. The webpage of this language that "solves" web dev is so spectacularly broken that it managed to crash Chrome for me completely. I have literally thousands of tabs open and it trucks along fine for weeks on end ... unless one of the tabs is elm-lang.org. 15 minutes later and every Chrome window and tab was still unresponsive, so I resorted to killing the process, then quickly closed that tab before it fully loaded on restart. Maybe it works for you? That's kind of even worse as it's not even consistent.

Oof, yeah, that's bad. But I doubt it could be very common or they would have noticed it and fixed it, eh?

Would you consider telling them about the issue? I realize that might be hard since their "community" links are on the bottom of the page that kills your browser, but no doubt they'd really appreciate hearing about it.

In any event, one regression (however painful) for one user doesn't invalidate the whole idea of Elm. It's still the right way to go even if it blows a tire from time to time.

Interestingly there is at least one effort to write an Elm-to-native compiler, so your Elm "web" app could also be compiled to native code & GUIs.