Skip to content
jc-rs
GitHub

Field notes

From raw output to a pipeline you can trust.

These are working notes, not a tour of every parser. Each guide starts with a real format or shell problem, shows the exact boundary jc-rs handles, and links back to the parser behind the command.

Formats

What changes when the same records move between files, streams, and configuration formats.

  1. NDJSON vs JSON vs JSONLChoose the right shape for streaming records, and see what changes in a real command-line pipeline.9 min →
  2. JSON vs YAML vs TOMLA practical format comparison for configuration files, machine output, and shell workflows.11 min →

Pipelines

Commands you can run, inspect, and adapt without hiding the awkward cases.

  1. Convert Linux logs to JSONParse syslog, web access logs, CEF events, and live streams without pretending every log has one schema.10 min →
  2. Bash, jc-rs, and jqTurn human-readable command output into JSON first, then query it safely with jq.8 min →
  3. Git log to JSONKeep Git's record structure intact without maintaining a fragile pretty-format escape scheme.7 min →
  4. ASCII table to JSONConvert aligned terminal tables into typed records, including the limits that decide whether parsing is safe.8 min →
  5. curl headers to JSONPreserve repeated headers and response boundaries when curl output becomes input to a shell script.7 min →

Decisions

Where a parser helps, where a native flag is better, and what tends to fail in production.

  1. Native JSON or jc-rs?Prefer a command's stable JSON flag when it has one; use a schema-aware parser when it does not.8 min →
  2. Why command-output parsers breakWhitespace, locale, wrapping, versions, and stderr are the failure modes hidden by a one-line awk script.9 min →