nent VS Recoil

Code example: view-source:https://nent.dev/

https://nent.dev is an entire app, with no framework or heavy scripting. It lets you do us on the HTML/CSS.

Source: https://github.com/nent/nent

Demo: https://nent.dev

I'd say, NENT, the un-framework for low-code web apps: https://nent.dev

Let me know if you want to swap open-source collaboration. I'm working on a project called NENT for the front-end that may also be a neat integration concept for Fusion: https://github.com/nent/nent

Wow! Check out the documentation, that is also a demo. Entirely an HTML PWA, that's installable, works offline, etc - and the only script is Google Analytics: https://nent.dev

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.