Ponder

Should Ponder replace SQLite with PGlite (pglite.dev) as the dev database? 

Pros:
1) Less magic/astonishment ("wait, what database am I using rn?")
2) Simpler schema definition API (currently stuck with the subset of stuff that both PG and SQLite support)

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

Sqllite I like because the path to ponder running in the background of a local first app is more clear

Good point. I'm actually not too worried about it though, seems like PGlite is very focused on browser support (WASM-first).

If anything a "con" for PGlite is that it's *too* focused on running in the browser, and they might deprioritize Node.js/Bun (where Ponder is more certain to run).

No, doesn't work and we can't figure out why. Process exits shortly after startup with no meaningful error code/message.

I have a strong hunch it has to do with `better-sqlite3` actually, so non-zero chance that moving to PGlite would also unblock Bun support. (github.com/ponder-sh/ponder/issues/442)

/max • /bracket • @quickcast • /coys • maxp.co

pglite'a purpose is specifically pg in the browser so if it tried to do anything else besides browser it'd be a con

it's parent product electric sql works outside the browser
next.electric-sql.com