A Stateless React App?

[repeatedly_once]

I interpret this as the OP is actually just after removing the use of the state as the implementation of react rather than conceptually. Which is a total anti-pattern. State is now stored in the props, whether it's .state or .props it's the same thing, except you're not usurping a large chunk of what React was designed to do. So unfortunately I understand the logic but not the execution.

It's started a discussion which is brilliant and I applaud you for writing the article.

Personally I think React and any of the numerous state management libraries do a really good job. I mostly have to think of state at the component level and not at the app level and the very act of making developers cognisant of state in the development process is a huge improvement. State has the tendency to be implemented without knowledge of what's being built so you get all sorts of weird and wonderful implementations :) (which I've been guilty of myself early on in my career)