That's not true either. In Redux the reducer is always pure and never modifies its arguments, at least in principle. It returns a new copy representing the new

That's not true either. In Redux the reducer is always pure and never modifies its arguments, at least in principle. It returns a new copy representing the new state. Dan Ahramov relies on deep-freeze to always assert this fact in all of his tutorials. Regarding next-action, in Redux subscribers are called after the root reducer returns the new state. You can always call dispatch from a subscriber. You and Sam are proving my point by not actually taking the time to understand the existing solutions.