3 ms·
As someone who spent over a year working on a production Elm app, I agree with this post 100%. Our team experienced all of these issues and more. The true cost
by xtian 7y ago
As someone who spent over a year working on a production Elm app, I agree with this post 100%. Our team experienced all of these issues and more.
The true cost of the approach Evan and the core team have taken is hard to measure, since what I observed most was skilled community members with the time and will to contribute silently abandoning the community after their efforts were roundly rejected or ignored. The record of these interactions tend to be scrubbed from GitHub and other community forums.
There are some really great ideas in Elm, but I would never recommend it to someone as a tool for production use. It is run more like a hobby project.
- javier2 7y agoI (luckily) only implemented a few smaller projects in elm around the time of 0.18 release. I started looking into how to get WebCrypto working, and was scared away by how they treated outside contributors. I liked Elm as a language, and Evan made a very good design. But to the core team, I got the message that they intend to work at their own pace, at their own leisure and will probably not take much input from outside contributors. This makes it very hard to expand the community and the usefulness of the language. They still have not afaik released anything for WebCrypto or WebWorkers. It is fine they are committed to the 100% pure language for frontend idea, but it makes it very hard to use if the Gods in the core team does not think it's fun/worthy to solve.