My point in the article is not that Redux is bad or that you shouldn’t use it, it’s that you can replace a lot of what Redux is most commonly used for if you use GraphQL instead of conventional REST. The state shaping and asynchronous request handling we were doing is not an incorrect way to use Redux, it’s one of the things Redux is used for most often (and it’s in the official docs, loads of tutorials, examples and boilerplates all over the web). Much of that type of usage is no longer necessary with a GraphQL + Apollo setup.

This is not just true for me; I’ve heard from many other developers that GraphQL has largely replaced the need for Redux for them as well. Switching to GraphQL from REST and to Apollo from Redux (even if you still use Redux) will reduce a ton of boilerplate in your codebase (pun intended).

Redux is still really helpful for dealing with REST APIs. This a not a dis on Redux. Redux is great. You seem to be somehow personally offended by something here and I think that’s a result of misunderstanding my point. Redux is a great library if used in the right places and no one should feel bad for using it but you can delete a lot of boilerplate if you use a GraphQL API + something like Apollo!