3 ms·
I agree with you in broad strokes, but as a piece of anecdata: I've had a lot of success building tools that emit and consume JSONL[1] instead of entire JSON do
by woodruffw 5y ago
I agree with you in broad strokes, but as a piece of anecdata: I've had a lot of success building tools that emit and consume JSONL[1] instead of entire JSON documents. JSONL preserves the Unix pipeline's inherently parallel design (people tend to forget this, even when waxing about the Unix philosophy!) but gives us all of the nice typing of a JSON stream.
That being said, I too will take a `sed` or `awk` one-liner over some of the `jq` monstrosities that I've seen.
[1]: https://jsonlines.org/ https://jsonlines.org/
- freshhawk 5y agoYeah, if we can't get something like edn (json but well designed and extensible) then jsonl is at least OK. > people tend to forget this There are people with strong opinions about this that don't even understand why you need something like JSONL in the first place and I'm surprised by that. If they never use unix pipelines I don't get why they feel we want to hear their hot take about how they should be redesigned.