3 ms·

> This criticism is spot on; it is exactly what I observed in late 2018, early 2019 as well. These issues were obvious much earlier than that. I looked into El

> This criticism is spot on; it is exactly what I observed in late 2018, early 2019 as well. These issues were obvious much earlier than that. I looked into Elm and was excited about it initially, in either late 2013 or early 2014. Then I looked into the history of some of the design decisions that baffled me (such as lack of type classes) and concluded the project was poorly conceived and led. The leadership didn't respect the opinions or capability of its end users.

wldlyinaccurate 7y ago
> The leadership didn't respect the opinions or capability of its end users This was the major sticking point for me when it came to Elm. I invested a lot of time into Elm and even published a few packages. Many things contributed to my giving up Elm, but the final straw for me was when the core team removed some userland APIs under the guise of "we can't trust developers not to use these to write bad code". Myself and several others tried to convince Evan to reverse this decision, to no avail.