rfcs VS effector-react

Re: global state management, I'd love your opinion on this RFC: https://github.com/statelyai/rfcs/pull/8

In its docs, Astro recommends nanostores, but I’ve used effector in the past. And LOVED IT. So I’ve used it for this project as well.

I've been using effector, together with the apollo-client for the last few years and, while it works, it's completely detached from the actual screens. In other words, you need to fetch everything (at startup) you might use at some point and it stays in the memory for the entire duration of the session. Error handling is also tricky as you need to explicitly subscribe to the specific error stores in order to render them. And, if something goes wrong, it's tricky to tell what data is actually used in the current screen, so it's almost impossible to do the Retry efficiently. OTOH the screens are nice and simple - no spinners, the data is just there, thus the app feels (and is) fast.

Actually, Svelte uses Effector for state management under the hood. You can read more about it here: https://effector.dev/. It also has bindings for other frameworks including React, Vue and Solid. Effector is a little not beginner-friendly, but once you truly understand it, Effector becomes a very powerful.

A state-management library.

Effector it is the another way to create state and business logic for your frontend application.

https://effector.dev/ here you go

Then I found Effector which seems to have the same features, and SolidJs support.

Where’s effector?

https://ngneat.github.io/elf/ https://effector.dev/