Elm is still really good for web applications, and the community is still active. I used Elm in production for many years and it is my choice for most producti

Elm is still really good for web applications, and the community is still active. I used Elm in production for many years and it is my choice for most production projects. Exceptions are - If you need to do a lot of number crunching and can't use Elm ports - If you need to use WebGL - If you depend on very specific JS libraries and can't use web components Many of the controversial decisions do make sense if you dig deep enough, but... You need to dig enough. I agree that there is an utter lack of transparency and communication from Evan and the core team. Worse, there is no acknowledgment of the problem nor any attempt to try and truly involve the community in the future of the language. Many enthusiastic people have left the community, leaving only those who can tolerate being told what is best for them. Personally, I stopped contributing to the community in any way. I started to write my own replacement language, http://squarepants.io/ http://squarepants.io/ which also tries to address some of Elm's weaknesses when scaling up (I was fortunate enough to use Elm on some large projects).