farcallerAfter 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.
GrUSP