71–74 of 74 posts
While I'm glad to see that there are many positives for using Elm, I'm curious about the "lessons learned" that come about from maintenance of the project.
Earlier quoted context omitted.
It's a neat little language. The benefits are real when coming from JS, but not that special when you consider other languages. Basically everything said in favour of Elm is completely true, but it's not the whole story. The ecosystem offers some trivial packages, but the hard stuff is missing. JS interop is intentionally quite painful. I'd consider it sufficient for fairly trivial SPA use, but lacking for anything l…
The bus factor of Elm is pretty bad compared to more "open" projects with RFCs, a dozen or so contributors, etc. In some ways it still feels like someone's private project. The problem with having a bus factor of 1 is that no one sees it as a problem until it becomes one.
It's used in two applications at CityBase. Given that I didn't write any of it, I can't answer the deeply nested component question. Our experience: It works well. However, we will probably stick with React or something else going forward.
What are the reasons you wouldn't consider using it going forward?
We've been using Elm in production for about 4 years (currently about 300,000 lines of code) and the experience has been wonderful! We rave about it. Also, we're hiring! No Elm experience required; over the years we've had many new hires pick it up on the job. :) https://www.noredink.com/jobs