We've been using Elm since Nov 2016 right after the 0.18 release to rewrite an old B2B web app. - The system has 150+ users that was migrated over night and ha

We've been using Elm since Nov 2016 right after the 0.18 release to rewrite an old B2B web app. - The system has 150+ users that was migrated over night and has been online for about 2 years now. - No runtime exceptions in production. In testing the only thing we had was "Stack size exceeded" in Internet Explorer due to a poorly written time zone module. - Translation was solved with one build for each language to avoid passing down the model everywhere. - Coding takes more time but things don't gradually turn into spaghetti and refactoring is a breeze. After the initial functional struggles it feels like writing "the code of your life". Overall, a very positive and fun experience and I don't regret us betting on this new fairly untested technology. And none in the team had lots of prior SPA experience so we had to learn new stuff anyway. Almost as good a tech choice as when we decided to use gevent or MongoDB but for a very different problem. This was for a custom client project and not our main 46elks service which is an API that mostly uses Python.