Date: Mon, 28 Jul 2014 07:53:37 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: "Simon J. Gerraty" <sjg@juniper.net> Cc: arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <20140728055336.GJ50802@ivaldir.etoilebsd.net> In-Reply-To: <20140728054217.AC1A0580A2@chaos.jnpr.net> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <CAETOPp13H7kyLy-1VJRDOsDbOh8A1MWZDxw1xHUBsxTRtMfc7g@mail.gmail.com> <20140728054217.AC1A0580A2@chaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--zOcTNEe3AzgCmdo9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 27, 2014 at 10:42:17PM -0700, Simon J. Gerraty wrote: >=20 > On Sat, 26 Jul 2014 19:29:04 -0700, Jos Backus writes: > >It's a little sad to see that the more human-friendly and expressive YAML > >format appears to not be supported. Instead, here too we are stuck with >=20 > Is there a use case for something like vmstat outputting YAML? > It is a simple format, I guess it could be added, especially if it has > no format quirks worse that HTML and JSON. > Note: I'm just speculating. YAML is all but a simple format, creating a subset of YAML that is good eno= ugh is a simple format :), exporting a complete YAML (strongly typed etc) is something else. As machine readable format YAML is a nightmare to parse, JSON is very simpl= er and easier (while json being a valid subject of YAML). regards, Bapt --zOcTNEe3AzgCmdo9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPV5WAACgkQ8kTtMUmk6EyfugCfWrlwpOwBZjZ/jCgEz5k2qm1V RjAAnA9RdYqV7tewWGMoiKbmyc1I/r9c =MAOM -----END PGP SIGNATURE----- --zOcTNEe3AzgCmdo9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140728055336.GJ50802>