It's an interesting topic. We use Elm at work, but I don't work with frontend development so I don't have a lot of hands-on experience with it. From following

It's an interesting topic. We use Elm at work, but I don't work with frontend development so I don't have a lot of hands-on experience with it. From following a few of those Reddit thread (the linked one and also [1] about a week ago) it seems like there is some growing concern about the BDFL-type development model that Elm is using. From a casual user's perspective and as someone with a background in Haskell development, Elm appears sort of unmaintained (PRs being ignored, no new releases/updates/anything in a long time) and unfinished (there are many "Haskell-features" that Elm has no equivalent to (yet), which leads to developers writing a lot of repeating code especially in areas such as JSON (de|en)coding). None of our work Elm code bases are particularly large (yet), and the developer doing the bulk of our frontend work is also a Haskell person by heart. We'll be staking out PureScript as an alternative, though we'd probably like to keep the idea of the "Elm architecture" alive there, too. It seems as if the Elm team is currently doing what SPJ once referred to as "avoid success at all costs" in order to ensure that they really nail the features they care about, but they're doing it after already having started a hype- and marketing wave several years prior, which is leaving people stranded in uncertain territory. We'll see how it works out ... [1]: https://www.reddit.com/r/elm/comments/7zk0dy/is_evan_killing_elms_momentum/ https://www.reddit.com/r/elm/comments/7zk0dy/is_evan_killing...