@foxdonut I am dispassionate about this argument, the concept of a reducer makes no sense at all because it does not represent how state mutates. Again state mutates following a simple cycle: propose, accept, learn. Redux's architecture's "accept" step is basically telling the store what to accept whatever has been proposed to it. That makes no sense. The accept step is fundamental to mutation: accept != assignment.