Date: Mon, 16 Nov 2015 10:46:58 +0100 From: Jan Bramkamp <crest@rlwinm.de> To: freebsd-current@freebsd.org Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <5649A612.3090905@rlwinm.de> In-Reply-To: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/11/15 13:54, Dan Partelly wrote: > 2. I have seen the idea that this makes the information dumped by utilities in the base easily accessible programatically. OK, maybe it does , but > it doesn't fit with the current paradigm of "tool | filter | tool” at all. There are no tools able to accept JSON and filter it in any meaningful way, and I > dont see too many ppl changing their code to read JSON instead of text. I don't even see the base tools changing. This output may be useful in corner cases only. There is jq [https://stedolan.github.io/jq/]. You can think of it as sed + awk + grep for streams of JSON objects.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5649A612.3090905>