Подходы к state management в React
У React-разработчика две беды: 1. Целевые данные изменились, а ререндера нет. 2. Целевые данные не изменились, а ререндер есть. Есть много вариантов подружить данные с интерфейсом, в рамках данной статьи я пройдусь по самым популярным из них. Выясним, как они устроены и для чего каждый из них подойдет лучше, обсудим конкретные реализации разных паттернов.
https://habr.com/ru/articles/984424/
#React #redux #zustand #mobx #valtio #jotai #state_management
Как создавали Jotai
Устали использовать Redux / Zustand / Jotai как чёрный ящик? Хотите наконец понять, что за магия там под капотом? Мне самому надоело вайбкодить синтаксис Redux-like библиотек. Пора уже понять чё за зверь такой – state manager. Это заняло у меня несколько месяцев, и сейчас пройдём этот путь вместе. Буквально изобретём концепцию Jotai за семь дней.
Je fais mon retour dans l'écosystème #React, j'ai découvert #Jotai et #Zustand
After spending the whole day reversing @sitnik_en's logux, I finally figured out how they solve the problem of the log store. They don’t, lol. There are some mentions of Redis in the commercial version, though.
I spent a bit too much time on this project; will have to wrap the story up soon. The TL;DR insofar was that #Jotai is a more straightforward state management than #nanostores and is **by far** better documented. It's easy to get up and running, easy to scale. It fits the medium-sized scope better than Valtio (just as I thought). It feels somewhat close to ClojureScript state management, which I still find ideal.
Having an app with shared state and local state is a pain either way. You can’t easily make Loro, Jotai, and React friends. You’ll make sacrifices. In the end, the reasonable approach seems to be to batch local changes in, e.g. Jotai and sync them up to Loro. I didn’t try Automerge yet, but both are Rust WASM. Loro has some very readable source code (I might be biased towards Rust, but Logux is hard to follow), though.
Aaaand there goes my weekend. I should totally get back into ZFS poking; all this frontend mess makes me crave the sanity of good old C.
I’ve reached enough complexity in my hobby app where valtio becomes a liability. Having a single global mutating state felt weird and yeah, it scales weird. The question is, of course, what lesson did I learn?
Probably that cljs had extremely good solutions when it came to state management.
Either way, I’m eyeing #nanostores and #jotai now.
【図解解説/入門】ReactとJotaiを使って実用的なNotion風ノートアプリを開発するチュートリアル【Convex/TypeScript/MDXEditor】
https://qiita.com/Sicut_study/items/ee41f1bb59fcda45a50b?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
2025年のReact状態管理、正直どれがいいの？ - Zustand, Jotai, Redux, Recoil, Valtio, XState, TanStack Query をざっくり解説
https://qiita.com/suin/items/e2df562b0c2be7e2a123?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Did you know I previously wrote a book about Zustand, Jotai, and Valtio? I think the content is still relevant (at least until the React Compiler lands 🙃).
In case you missed it, you can find the link on my site 👉 https://daishikato.com
#ReactJS #React #JavaScript #TypeScript #Zustand #Jotai #Valtio
Check out our new kid in the Jotai ecosystem: jotai-history.
Give it a try and share your feedback!
Habr
Stéphane Klein
farcaller
Qiita - 人気の記事
Daishi Kato
