It's easy to forget to access something through a proxy or a snapshot, and this causes subtle bugs.
Big cognitive load trying to read the code that's using valtio, unless you just assume it does the right thing.
Hard to tell what you're subscribing to when you access a nested object in a snapshot
Lots of over-rendering and very hard to tell why.
Can't actually use valtio with plain js, because it can't dig down into things to proxy internal references, especially those captured by a closure
In general... it's hard to grok, hard to use, hard to read - at least the way I'm trying to use it. It might be better with less coupling of state and behavior - dumb state objects, and code that acts on and reads from those objects, instead of objects that mix state with behavior. This is probably nice for saving and loading anyways?
Anyways, figure out how to use the library better and do so, or figure out what to use instead and do so.
Many disconnected thoughts here:
In general... it's hard to grok, hard to use, hard to read - at least the way I'm trying to use it. It might be better with less coupling of state and behavior - dumb state objects, and code that acts on and reads from those objects, instead of objects that mix state with behavior. This is probably nice for saving and loading anyways?
Anyways, figure out how to use the library better and do so, or figure out what to use instead and do so.