Re: Structured (ie: json) output for query commands?

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Jun 30, 2021, 23:27 UTC
Message-ID: <CACPiFCLAm+e_JRc=eAt_rqwCWASqr19nXdk0zWqLbTEgELL81w@mail.gmail.com>
In-Reply-To: <YNzR5ZZDTfcN2Q+s@camp.crustytoothpaste.net>

On Wed, Jun 30, 2021 at 4:20 PM brian m. carlson <sandals@crustytoothpaste.net> wrote:

> I'm personally fine with the ad-hoc approach we use now, which is
> actually very convenient to script and, in my view, not to terrible to
> parse in other tools and languages.  Your mileage may vary, though.

It's of one piece with the Unix tradition that gave us Perl. That's both a blessing and a curse.

Outputting fields, escapes, etc and the ability to use xpath to extract, manipulate and query specific data is... very useful. There's a hard tradeoff with utf-8, and any attempt at papering over that - iconv conversions, etc – will inevitably munge data in some cases.

hmmm,

-- 
 martin.langhoff@gmail.com
 - ask interesting questions  ~  http://linkedin.com/in/martinlanghoff
 - don't be distracted        ~  http://github.com/martin-langhoff
   by shiny stuff