react-hook-thunk-reducer VS Recoil

I've been playing around with useReducer and useContext and it was trivially easy to implement a functional action/reducer system that worked just like redux but glued together with react built-ins. I'm also not sure what the difference between a custom hook and a middleware is, they seem like the same thing to me. Custom hooks are easy to implement, for example here's the equivalent to a thunk "middleware": https://github.com/nathanbuchar/react-hook-thunk-reducer/blob/master/src/thunk-reducer.js. You can keep wrapping your reducer in as many custom hooks as you like to handle whatever side-effects you need, just like you can with redux middleware.

Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.

recoil -> Designed to solve a specific problem. Not good for all use cases. Understand it first! You can learn more about it here.

Recoil Official Website

Recoil 🌀

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

However you may find better luck with Recoil which is developed by Meta, and is designed to work with Async data, and is a much simpler project to get started with.

Recoil introduced a new pattern for storing state and propagating updates. This atomic model has proven to scale up better than the singleton model at the cost of some hefty learning curves.

recoil is extremely similar to Riverpod but for React (both are backed by a data flow graph).

Before we proceed you can check the project on github. This implementation is for learning purposes, for production use check Jotai or Recoil.