Skip navigation
For years i've had this vision for a synchronous reactive ORM with offline support and realtime…
0:00 / 0:14

For years i've had this vision for a synchronous reactive ORM with offline support and realtime…

Austin Malerba

@austin_malerba11K followers

Visit on X

15,179 views

For years i've had this vision for a synchronous reactive ORM with offline support and realtime syncing to other clients. This is the holy grail of state management IMO and i'm finally building it using mobx and yjs. I know that's a mouthful so let me explain: synchronous - there's no promises to deal with and therefore no loading states which leads to much cleaner frontend code. reactive - imagine signals/observables that you can mutate and they will trigger your components to rerender and also will immediately propagate to other users' devices. ORM - what i've made is not an ORM, but it looks and feels like one where you define Models and then you interact with instances of those models. offline/syncing - this is done through yjs, a CRDT implementation, and websockets. CRDTs power many modern collaborative multiplayer tools like figma.

Comments

Comments from the original post on X (Twitter)

No comments yet