The problem
With state in components, data that many components share lives high up the tree and is changed by setState calls scattered over many components, triggered by clicks, server responses and timers. As apps grew, simple questions became hard to answer: what changed this value, and why does the screen look like this?
The idea
Flux (Facebook, 2014) sends every change down one path: a view creates an action, a plain object that describes what happened; the dispatcher hands it to the stores; the stores update their data and the views render again. Data flows in one direction.
Redux (2015) made it simpler: the whole state is one object in a single store, and a reducer, a pure function (state, action) => nextState, computes the next state. Components do not change data: they dispatch actions, and connect passes them the parts of the state they read.
What hurt next
Every small feature needed the same pieces in several files: an action type constant, an action creator, a case in a reducer, and mapStateToProps / mapDispatchToProps to connect a component, plus objects copied by hand so that nothing was mutated. Setting up a store with middleware and the DevTools took more code still. Redux itself later answered with Redux Toolkit; component frameworks like Vue, Angular and Svelte offered reactive state you change directly and HTML templates that update themselves, with much less ceremony.
How close this is to the original
Runs Redux 5.0.1, React-Redux 9.3.1 and React 19.3.0 with the API of 2015–2018: createStore, combineReducers, <Provider> and connect(mapStateToProps, mapDispatchToProps); the component reads the input through a ref, like the AddTodo example in the Redux 3 docs. createStore (since Redux 4.2) and connect (since React-Redux 9.3) are now marked @deprecated, but only as an editor hint: they behave as before and print nothing, and legacy_createStore / legacy_connect are the same functions without the mark. Redux code today uses Redux Toolkit's configureStore and createSlice with the useSelector / useDispatch hooks. Facebook's own flux package with its Dispatcher is not used: the project is archived and its README recommends Redux among others. As in the other React demos, the entry uses createRoot, because React 19 removed ReactDOM.render.