2 ms·
I’ve used it on a deployed and used project app. On a substantial commercial internal project. And have 2 other apps in the works. I’ve used ports and custom e
by z5h 8y ago
I’ve used it on a deployed and used project app. On a substantial commercial internal project. And have 2 other apps in the works.
I’ve used ports and custom elements to integrate JS code.
I’m convinced Elm is an excellent way (and my preferred way) to build frontend apps.
The learning curve is a bit tricky. I think the path to toy apps is straightforward and fun. The path to “real world” apps requires a bit more effort. Expect to do some homework, hang out in forums etc.
- pault 8y agoI've been picking it up lately and I'm curious if you have any links to non-trivial application sources. I'm curious how the architecture scales and how it handles cross cutting concerns.
- z5h 8y agoYou'll probably want to watch Richard Feldman's [Scaling Elm Apps](https://www.youtube.com/watch?v=DoA4Txr4GUs https://www.youtube.com/watch?v=DoA4Txr4GUs). I built [Component Result](https://package.elm-lang.org/packages/z5h/component-result/latest/ https://package.elm-lang.org/packages/z5h/component-result/l...) to help with a pattern that occurs when scaling up apps. I'm not clear what you mean by or expect to be problematic with by cross-cutting concerns. Feel free to ping me, z5h, on the Elm slack.