Post

Axel
@axelinternet.bsky.social

Great example! I think the even more common cousin of this I see a lot is using some useEffect to handle this when the state could just be derived or set directly.

Sámal Rasmussen
@samalrasmussen.bsky.social

The is pretty damning for all those local first sync engines. Everything is a big blob of implicitly synced state. No thank you. I want to explicitly subscribe to specific resources, and I want to make read/write requests that I can wait for the results on. This is how I tend to my data pipelines.

Tom Hicks
@hicksyfern.bsky.social

Not really the same thing I don’t think. In the sync engine case you just work from the local state (making sure to derive rather than sync things around the UI) and let the sync engine work in the background. The sync is a completely separate concern that the UI never sees.

Tom Hicks
@hicksyfern.bsky.social

I don’t get it. You don’t pretend like you didn’t. You pretend like your local changes will make it to the server and be synced. There’s lots of abstractions we use. This is a strange one to pick on.