Loro: Reimagine state management with CRDTs
1–10 of 45 posts
Re: Loro: Reimagine state management with CRDTs
#2The performance of this looks really interesting, looking at the demo gif they have on the page.
I wonder if this is something that can be used for versioning database columns / fields.
Re: Loro: Reimagine state management with CRDTs
#3great post explaining CRDT and the tool.
Re: Loro: Reimagine state management with CRDTs
#4We've been using https://github.com/electric-sql/electric for real-time sync for the past month or so and it's been great. Rather than make you think about CRDTs explicitly, Electric syncs an in-browser sqlite db (WASM powered) with a central postgres instance. As a developer, you get local-first performance and real-time sync between users. And it's actually faster to ship an application without writing any APIs and just using the database directly. Only downside is Electric is immature and we often run into bugs, but as a startup we're willing to deal with it in exchange for shipping faster.
Re: Loro: Reimagine state management with CRDTs
#5We've been using https://github.com/electric-sql/electric for real-time sync for the past month or so and it's been great. Rather than make you think about CRDTs explicitly, Electric syncs an in-browser sqlite db (WASM powered) with a central postgres instance. As a developer, you get local-first performance and real-time sync between users. And it's actually faster to ship an application without writing any APIs and…
How do you handle migrations?
Re: Loro: Reimagine state management with CRDTs
#6I see that the libraries are written in Rust, would this work in a nodejs app as a wasm or as native plugin?
Re: Loro: Reimagine state management with CRDTs
#7We've been using https://github.com/electric-sql/electric for real-time sync for the past month or so and it's been great. Rather than make you think about CRDTs explicitly, Electric syncs an in-browser sqlite db (WASM powered) with a central postgres instance. As a developer, you get local-first performance and real-time sync between users. And it's actually faster to ship an application without writing any APIs and…
How do you handle migrations?
The docs say Electric propagates migrations (DDL) on Postgres synced tables to their “satellite” clients
Re: Loro: Reimagine state management with CRDTs
#8We've been using https://github.com/electric-sql/electric for real-time sync for the past month or so and it's been great. Rather than make you think about CRDTs explicitly, Electric syncs an in-browser sqlite db (WASM powered) with a central postgres instance. As a developer, you get local-first performance and real-time sync between users. And it's actually faster to ship an application without writing any APIs and…
How do you handle migrations?
Every postgres migration is done through an Electric proxy and it converts it into a corresponding sqlite migration that it can apply later on the client. In case of a migration that would be somehow breaking you can also drop the client-side sqlite database and resync state from postgres.
Re: Loro: Reimagine state management with CRDTs
#9The demo code for Loro looks very easy to use, I love how they infer a CRDT from an example plain JS object. I’ve played with a Zod schema Yjs CRDT translator and found it kinda annoying to maintain. However this looks so easy I worry about apps building with too little thought about long term data modeling. Migrations on CRDTs are challenging, so it’s important to “get it right” at the beginning. I’m curious how this design works with longer term, more complex CRDT apps.
Re: Loro: Reimagine state management with CRDTs
#10Curious how this compares with Automerge/Automerge-repo [0]. Looks like Automerge is at 2.0.