I never said you cannot implement SAM with React/Redux, from what I understand some people use SAM with React and also Redux.
I am just arguing that the granularity and the general recommendations around Redux are too coarse to isolate mutations. A reducer typically spans a SAM action, mutation and state representation, not to mention NAP. All this code is conveniently wrapped in a pure function. That's the only point I am trying to make.
SAM is very gentle when it comes to code structure, I never felt constrained by the pattern, quite the opposite, each time I tried to take a shortcut, I ended up paying the price. In all honesty, I have never been in the situation where I felt, "why did I use this pattern".
I come from a "stateful" background (B2B, BPM, EAI). I also have quite a bit of front-end experience (Mobile, Web, Thick Clients). Managing state has always a problem until I stumbled onto SAM. I am sure it can be perfected, but from my perspective, it has given me a reliable coding style without much constraints.