Just curious why not use useSyncExternalStore like Zustand?

[L-Qun]

https://codesandbox.io/s/react-tearing-jotai-wqwwqt?file=/src/Controller.js

You can see that there are tearing issues between the individual components, and React18 also remove eagerState for useReducer.

[dai-shi]

uSES fixes tearing but doesn't behave nicely with promises which is one of the goals of Jotai.
I made non-uSES version of zustand too: https://github.com/dai-shi/use-zustand

[iwoplaza]

I would love a blog post on the behavior of useTransition and Jotai, or other state management libraries. I tried incorporating useTransition into our app using Jotai, but I have not managed to figure out how to make that work.

Does using useTransition alongside useSyncExternalStore cause some stale-UI or invalid state, or is it just harder to wrap state updates in a transition while using uSES?

[dai-shi]

If you use useSyncExternalStore, basically time slicing doesn't work.
https://github.com/dai-shi/will-this-react-global-state-work-in-concurrent-rendering
☝️ Compare jotai and zustand

See also: facebook/react#26814

[L-Qun]

So the reason you don't choose useSyncExternalStore is because it doesn't support time slicing

[dai-shi]

Yeah, that what I meant with "behave nicely with promises" for useTransition.

[dai-shi]

https://blog.axlight.com/posts/why-use-sync-external-store-is-not-used-in-jotai/ I'm basically rephrasing what I said above.

[L-Qun]

@dai-shi And another question is why you use useReducer instead of useState. I think the performance of useState is better than useReducer because the React team has already removed eager state policy from useReducer: facebook/react#22445

[L-Qun]

Looking forward to your reply❤️

[dai-shi]

I think we actually depend on the lazy updates. Or what I call the cheat mode. There must be some tests failing if we change useReducer to useState.