Very nice bit of archeology!

Back in 2017, about a year after I took over as Redux maintainer, I wrote up a post exploring some of how Redux works, its design constraints, and the intended goals and influences:

- https://blog.isquaredsoftware.com/2017/05/idiomatic-redux-ta...

I also wrote a follow-up post explaining why some of the common usage patterns around Redux existed:

- https://blog.isquaredsoftware.com/2017/05/idiomatic-redux-ta...

As part of that work, I did a bunch of research back into the early Redux issues, and took notes on things like the first use of the words "reducer" and "thunk", how `connect` got its final API design, the intent behind "actions", and a lot more:

- https://gist.github.com/markerikson/2971210292a9c65138eeb33a...

All that said, over the last 3 years we've drastically changed how you write Redux code. Today, "modern Redux" with our official Redux Toolkit package is drastically simpler, and much easier for folks to learn and use. We've rewritten our tutorials from scratch, added a React-Redux hooks API, and even built "RTK Query", a full data fetching and caching solution built on top of Redux Toolkit:

- https://redux.js.org/introduction/why-rtk-is-redux-today

- https://redux.js.org/tutorials/essentials/part-2-app-structu...

I've also written up a few other history/archeology-style posts on how React-Redux has evolved over the years, how we designed and built Redux Toolkit, and how we designed the RTK "listener" middleware:

- https://blog.isquaredsoftware.com/2018/11/react-redux-histor...

- https://blog.isquaredsoftware.com/2019/10/redux-toolkit-1.0/

- https://blog.isquaredsoftware.com/2022/03/designing-rtk-list...

So, if anyone is interested in more details on how Redux has evolved, gotcha covered :)