To be fair, you need to leave off the complications of edge UI development overall (webpack configs and loaders, css frameworks, transpiling, etc.). As for React/Redux you could make the argument that it's simpler because you're working in a single store as opposed to many. However, the pieces of that process are highly fragmented (action types, actions, action creators, store, reducer(s), side-effects like sagas or thunks, HoCs like connect, etc). It's a lot to keep in mind, granted.
For really large projects with multiple devs this kind of set up makes a lot of sense because your application is already complex. It tends to keep things within convention so that it doens't matter who writes the logic, you can find out quickly what's happening. Even so, I do have a suspicion that as time goes on things might become a little less decoupled and a more solid, opinionated framework may takes its place.
For smaller projects where this isn't needed or might be overkill feel free to use other setups that might be simpler. MobX is a promising alternative. :)