Spent the am building reactive code cells that can depend on one another for the new documentation site. Like ObservableHQ but I didn't want to include their notebook interface.

One of the things I'm most excited for is partnering with the LibSQL folks to create a custom syntax for defining tables which are backed by CRDTs! LibSQL is truly getting SQLite ready for the coming decades -- github.com/libsql/libsql vlcn.io/cr-sqlite/cust…

I was blown away by Aaron Boodman's talk and the Replicache model so I spent the last day experimenting with a variation on the idea: "Creating CRDTs without specialized knowledge" vlcn.io/articles/crdt-…

I was accepted to give a talk about github.com/vlcn-io/cr-sql… & local-first software at #DWebCamp2023! 🎉 See you there! DWeb → ⁂ @[email protected]

In the refinement phase of cr-sqlite - - decreasing crdt metadata size by 5x - improving crr creation syntax - adding support for resurrecting deleted items - adding list CRDTs to the DB so you can have collaborative text w/o yjs or automerge - improving schema migrations

github.com/groue/GRDB.swi… is an amazing piece of work in terms of improving the reactivity story for SQLite.

"Most databases were built when data was static and queries were dynamic. For applications, most queries are static and the data is dynamic" - Matthew Linkous I never thought about it this way before but this is spot on.

How much easier is life when your database does that for you?

Interesting realization that if you're syncing CRDTs through a central server you can apply whatever sort of validation logic you want on the server to preserve constraints. The validation logic just needs to write fixes as a new database version to sync back to clients.

Episode #10 is out. Matt Wonlaw (Matt Wonlaw) on building his own local-first tools (cr-sqlite, Materialite) and comparing syncing mechanisms.