Thanks for the comment. I haven't been following Elm news so I don't know if there have been any recent developments. However, I did watch Evan's recent video on the hard parts of open source. It reinforces my assessment that there is a top-down authoritarian perspective on managing the community, and it isn't the place for us.
Analysis of the video: Evan brings up Orwell's 1984 as cultural shift to a distrust of authority. The context of his talk seems to imply that mistrusting authority is part of the problem. The communication patterns he brings up at the end are very controlling of the end user, ostensibly for the good of the community. This makes the intention seem deeper than just controlling the destiny of the Elm product. It means also controlling a collectivism-based Elm community using authoritarian strategies. This agrees with my own experiences and observations. For me, this is a bit too intense of a requirement from a technology.
I have started a project in F# using Fable-Elmish libraries, and it is equivalent (and syntactically similar) to Elm but with a lot more freedoms. In fact I can go a step further now and test that the update function produces not only the correct model, but also the correct declared effects. TBH we don't do unit testing of Elm UIs, because we haven't had the need. But I appreciate being able to declare my own effects and write their implementations in F# off in its own corner, rather than having to go across ports and switch to JS. Also auto-JSON decoders.
We’re a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.