To be clear I don’t use Elm in production so my thoughts are purely speculative. However, when you remove FFI to JS - in a language which is focussed around the web platform, which evolves pretty quickly - and you only have a handful of developers, it strikes me that just keeping up with the Web API bindings alone, is a lot to undertake. For example, if you want the new Web Transitions API, I guess you’ll have to hope you can call it through JS ports.
As others have noted, the Elm architecture has influenced many more pragmatic frameworks that have taken the key principles while still allowing work to get done.
I’ve used Elm a few times for hobby projects and while it’s super nice to model state and render most HTML and CSS (and is even enjoyable to write), you always feel that one day you’ll become too locked in and that Evan may decide to go live on a farm.
As others have noted, the Elm architecture has influenced many more pragmatic frameworks that have taken the key principles while still allowing work to get done.
I’ve used Elm a few times for hobby projects and while it’s super nice to model state and render most HTML and CSS (and is even enjoyable to write), you always feel that one day you’ll become too locked in and that Evan may decide to go live on a farm.