redux-essentials-example-app VS reactn

You're right, it is related. But I think that Flux- and ELM-like architectures are making it even worse by forcing any "external" interaction to became the gap. Look how they suffer when it comes to executing any async operation like network request. Initially we have this relatively simple framework, but then we had to add "Middleware" to just run network request (which is a good example of the Remainder issue). I love the idea behind these architectures, which makes logic more predictable and testing way easier. I even was using them by myself. But now they looks like something turned inside out for me. I believe we could do better. I'm finishing my proposal right now. It will take couple more weeks to edit and translate it, but soon I'll show what I mean.

Hi, I maintain Redux and wrote most of our docs (including our current tutorials).

Can you give some details on which parts of our docs you feel are "incomprehensible"? I'm curious which specific pages you've been looking at, and for what purpose.

We've tried to organize the docs using the "Documentation System" approach described at [0]: Tutorials for teaching step-by-step, Explanations and How-To guides for specific topics, and References for API details.

Generally we want people to go through our "Redux Essentials" tutorial [1] as the primary way to learn how to use Redux correctly. It teaches "modern Redux" patterns with Redux Toolkit as the standard way to write Redux logic (including RTK Query for handling data fetching), and React-Redux hooks in components.

I'm genuinely interested in feedback on what explanations aren't clear and how we can improve things!

[0] https://documentation.divio.com/

[1] https://redux.js.org/tutorials/essentials/part-1-overview-co...

https://redux.js.org/tutorials/essentials/part-1-overview-concepts (covers how to use Redux Toolkit and RTK Query)

Have a look at ReactN

If you want to move to hooks for state management I suggest ReactN.

ReactN because it demonstrated engaging with and supporting customers to balance priorities and deliver results.

My open source React state management library ReactN helped me get a job at AWS, because it showed customer obsession.

I love ReactN.

Look into ReactN which uses hooks, has lower overhead, no boilerplate, and is much easier to use and learn than Redux.

I myself started a few years ago using ReactN which intends to implement global state management in a similar way like the local state in react works. But since this is a monolithic store too I recently switched to (the very unknown) React Capsule which is from the same dev, extremely lightweight, similar to recoil and intends to use encapsulated state which can be used either in plain JS, in class components, as well as in function components.