Elm from a Business Perspective
Well.<p>Summary: &quot;I have no idea about the technical criticism or type classes, but we use Elm and it works for us. It&#x27;s easy, you are productive quickly (quicker than with React&#x2F;Angular), it prevents bugs, devs like it, and so it saves us money.&quot;<p>It&#x27;s nice to hear that a company is able to utilize Elm effectively.<p>It would be nice to know how big their 5 Elm projects &quot;in various stages and different scale&quot; are to judge whether Elm in it&#x27;s current form is a good fit for larger apps. Especially since the Elm library ecosystem is still very immature, so experience with building good, reusable libraries is not that great.<p>Would also be nice to know how they deal with boilerplate, which is a big annoyance with Elm in my opinion when you come from, eg, Haskell.<p>In terms of maintainability (refactoring, etc) you can&#x27;t get much worse than Javascript, so Elm will probably be a win there, regardless of a limited type system.<p>As long as you don&#x27;t have to build and maintain lot of required libraries yourself, that is.