As a casual user of Elm it was interesting for me to read from someone who knows more about its development process. Unfortunately the author is frustrated by t

As a casual user of Elm it was interesting for me to read from someone who knows more about its development process. Unfortunately the author is frustrated by the process. And that frustration resonates with me. I've personally run up against these end-of-discussion comments that do not address the points that were raised in the thread. Obviously, the developers of Elm can choose their development style. And those who can't live with that style can fork or fuck off. Still it is sad to see people sore from conflict. The author has a lot of investment in Elm, otherwise they wouldn't have written this. When I need to decide on my involvement in Elm, I will consider how conflicts are resolved. I understand the purism of Elm, and I know it is part of why I like the language. I accept it takes unpopular decisions to keep it "pure". On the other hand, when I see people break off over limitations that the Elm project places on its users, but not on themselves (one of the main points of that article) I do get a sad feeling. What kind of relationship is this where you trust yourself with compiler features you don't allow other people to handle? Words like patronizing, controlling, and self-serving come to mind. They may have the best of intentions and my protection in mind, but I prefer the privilege to know I can shoot both my feet if I need to.