curiousreacter

4 ms·

1. 1.▲
   by curiousreacter 8y ago

   Well, I'm thinking that Redux would apply the diffs to the state destructively, so I'm not sure why we would need to "constantly" reapply them in order to recreate the latest state... we would simply have the latest st
2. 2.▲
   by curiousreacter 8y ago

   Hmm, but reducers are supposed to return references to new state objects, right? So clearly something more substantial than a pointer has to be created/duplicated.
3. 3.▲
   by curiousreacter 8y ago

   Oh right, immutable data structures are good for exactly this situation. I've been in mutation land for a while now. :) However, now I'm newly confused: Yes, I'm proposing that the diff then get applied directly to the state
4. 4.▲
   by curiousreacter 8y ago

   Side question: Isn't it grossly inefficient that in Redux, you have reducers that return an entirely new state object? Wouldn't it be better to return some kind of data that represents just the diff you intend to make, like {op: I