-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why Unstated? #90
Comments
I agree. This library is just a wrapper around the React context api which doesn't add any new functionality. I like these three state management libraries better: Zustand, Valtio and Jotai. |
I looked into one of these libraries, Zustand, and the setup for Next.js is HUGE https://github.com/vercel/next.js/blob/master/examples/with-zustand/lib/store.js |
Agreed. Use React Context; it has almost the exact same API as unstated-next. I guess unstated-next only exists because unstated existed, and maybe they look somewhat alike 🤷🏿 |
I'm just failing to understand why use unstated. The implementation looking at the source doesn't seem to do anything to add to the existing context API, no memoized selectors, no atomic API. So why is unstated so popular and what does it add?
The text was updated successfully, but these errors were encountered: