elm-spa-example

The parents of each of these elements have to manually map the state changes, they have to be aware of the internal state of the components, just as I was saying. Check this out: https://github.com/rtfeldman/elm-spa-example/blob/master/src... Go to the bottom, see how it manually maps the child events of the feed update? You have to duplicate that code for every single child component. All the other steps I described are there also.

> In order to create a list of stateful children, you must: This is trivially debunked: here is a 4,000 LoC open-source Elm SPA with small, type-safe reusable views that have state and don't do all this. :P https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa Plenty of counterexamples in there. Here's one. https://github.com/rtfeldman/elm-spa-example/blob/master/src... Here's another. https://github.com/rtfeldman/elm-spa-example/blob/master/src... Here's yet another. https://github.com/rtfeldman/elm-spa-example/blob/master/src...

I'm using Elm for an internal customer service app and it is working out fairly well. My background is more server side programming so the ability to avoid javascript and its constantly changing ecosystem is a big plus. Elm the language is simple enough to understand in a day and the basic architecture is also straightforward. The biggest challenges are finding examples of how to architect larger apps but this example should help https://github.com/rtfeldman/elm-spa-example Also, I tried mentoring another coworker on Elm but they seemed to have a harder time than I did. I think it could be partly because they were an experienced Javascript developer who wanted to apply their existing patterns to Elm.