I made a little tool for Ralphing on Sprites: https://github.com/thruflo/wisp

I’ve found the sprites just work for claude. Pull how a repo (or repos) and run dangerously.

This is very much the point of https://pglite.dev

It's an embeddable Postgres you can run in process as a local client DB, just like SQLite but it's actually Postgres.

For sure. I’m curious if anyone using it in production as an alternative to SQLite and, if so, what the performance and experience is like.

I wish this were available for Go lang, perhaps via Wazero.

Me too. There's only so much time in life. I'd take it for a spin if someone else did it. :)

Ah, I thought I recognized your username from a Github URL. :D Thank you for your contributions in the SQLite & Go space!

Dallin's building https://www.buster.so (agents for data analytics).

Just to say if you're interested in this kind of tech and are in the Bay Area, Sync Conf [0] just announced [1] its initial speaker lineup today and Arushi Bandi from Figma is one of the speakers.

[0]: https://syncconf.dev [1]: https://x.com/sync_conf/status/1957818840777122293

PubSub and LiveView do go a long way. However, broadcast isn't sync and LiveView isn't appropriate for all applications.

Phoenix recently added Phoenix.Sync [0], a sync engine library explicitly designed [1] to address this. In combination with a front-end library like TanStack DB [2] it goes much further towards giving you a Figma/Linear-style sync engine out of the box [3].

[0] https://hexdocs.pm/phoenix_sync [1] https://www.youtube.com/watch?v=4IWShnVuRCg [2] https://electric-sql.com/blog/2025/07/29/local-first-sync-wi... [3] https://electric-sql.com/demos/burn

Disclaimer: Electric founder. Linking to my own talk / post / demo.

A sync engine plus the always online nature of LiveView feels at odds with offline-first (which is often associated with sync engines). I wish LiveView had a better offline story.

> Electric’s approach is compelling given it works with existing Postgres databases. However, one gap remains to fill, how to handle mutations?

Just to note that, with TanStack DB, Electric now has first class support for local writes / write-path sync using transactional optimistic mutations:

https://electric-sql.com/blog/2025/07/29/local-first-sync-wi...

I'm biased but https://electric-sql.com/blog/2025/07/29/local-first-sync-wi...

This is the VM behind Popcorn https://github.com/software-mansion/popcorn, a project aiming to run OTP and Elixir in WASM:

> Popcorn is a library that allows you to run client-side Elixir in browsers, with Javascript interoperability

Recent ElixirConf keynote introducing it: https://youtu.be/ep--rQO1FRI

On your last point: https://pglite.dev

On the main point around materialisation cost, I know more work is planned on compaction specifically but generally LiveStore is a framework that’s been highly crafted to address and optimise for all aspects of performance.