Post

i wish i felt like it had the same immediate graspability as jsonl. i can't find ways to really disagree but i still really don't want to! the one core difference is streaming/eventsourcing i guess? i have strong interest in ltx etc but getting architecture astronaut-ish. github.com/superfly/ltx

but ndjson is okay right?

But where does DuckDB rank?

Until you need to grep it at 2am. JSONL survives a half written last line, while a SQLite file copied mid write can come back corrupt.

JSONL wins exactly one fight: appending from a shell one-liner with zero schema. Everything after that, like pulling last Tuesday's rows without reading the whole file, belongs to sqlite.

The switch usually happens the first time you need the last 50 errors from one user and catch yourself piping jq into sort into tail. One WHERE clause later, jsonl is an export format.

TIL there's a name for this.