3 ms·

I imagine building this was a useful learning experience (and your intro blog post alludes to that), but keep in mind that Redux is much more a way of thinking

I imagine building this was a useful learning experience (and your intro blog post alludes to that), but keep in mind that Redux is much more a way of thinking about state transitions than it is a library for providing them. The Elm architecture was the original inspiration for Redux, and I recommend running through the rest of the Elm examples [1] to decide if your removals from Redux are worth pursuing. Notably, how will you handle composing your action-reducers? Can you build the "dynamic list of counters" example without compromising the simplicity you're looking for? [1] https://github.com/evancz/elm-architecture-tutorial/blob/f8a944bf0e89062f4f3a60716b7e06d37593627f/README.md https://github.com/evancz/elm-architecture-tutorial/blob/f8a...

leshow 9y ago
I'd just like to comment that TEA (the elm architecture) has changed a bit now, and been baked into the langauge. They've made it very tedious to abstract any state away from global, and so those examples have been removed (if you look at TEA NOT from 2015). It's an unfortunate thing in the Elm community that they encourage you to either: A: have an update function that could grow forever depending on the sizeof your app, B - have to write many lines of boilerplate and get 'discouraged' from even doing so by the community because it's not the language's blessed path. Here is the new TEA doc: https://guide.elm-lang.org/architecture/ https://guide.elm-lang.org/architecture/ Note it never mentions components or how to compose update functions.