> With them you write all this lasagna code to wrap the mutation of data and to make the UI react to all these changes.
Yeah, and allowing developers to just access state from anywhere and mutate it doesn't generate lasagna code at all.
The issue so far with RxDB I see is how silly complex the syncing gets. You just see it doing its thing and hope whatever payloads it sends are optimal for your use case. And while offline-first seems neat in theory, it's not necessary for most web apps IMO. For desktop or mobile apps it's a different thing, but they have other options too that browsers don't allow.
Yeah, and allowing developers to just access state from anywhere and mutate it doesn't generate lasagna code at all.
The issue so far with RxDB I see is how silly complex the syncing gets. You just see it doing its thing and hope whatever payloads it sends are optimal for your use case. And while offline-first seems neat in theory, it's not necessary for most web apps IMO. For desktop or mobile apps it's a different thing, but they have other options too that browsers don't allow.