1. 13
  1.  

  2. 5

    I have limited experience with Elm and more experience with Redux. It seems like the post kept going in circles around the solution, which is not to break up the state like that in the first place. The talk of data ownership and encapsulation is really a red flag when you have atomic state as the foundation of the Elm Architecture.

    So, to my mind, the solution for both Redux and Elm is to just have everything access the whole model. That’s certainly how I’ve been using Redux, but maybe I’m missing some issues with applying this approach in Elm?

    1. [Comment removed by author]

      1. 2

        Elm is not lazy though.

        1. 2

          Duh. Sorry, I had the mistaken impression it was. Thank you!