Date: Mon, 28 Jul 2014 22:57:23 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Jos Backus <jos@catnook.com> Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org>, Jordan Hubbard <jkh@mail.turbofuzz.com> Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <CAJ-VmomiwUWHWYLdLcQAnp7QBmvQR2wfPoCy=eie-jrvyw0HfA@mail.gmail.com> In-Reply-To: <CAETOPp0c1xfMj1vDvQRSoV3ec-LdJmyT9AFH02iziN0yuY1D-A@mail.gmail.com> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <CAETOPp13H7kyLy-1VJRDOsDbOh8A1MWZDxw1xHUBsxTRtMfc7g@mail.gmail.com> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <CAETOPp3hJB8Gj%2BPMj3N951krnNqCYiAOY-cPHxMCBy1CQXWJaQ@mail.gmail.com> <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.com> <CAETOPp0c1xfMj1vDvQRSoV3ec-LdJmyT9AFH02iziN0yuY1D-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Holy ... ! What really matter is whether the library API that you're going to shoehorn into plenty of utilities is expressive enough to express a whole bunch of different output types. So it doesn't matter if you want JSON, or YAML, or XML, or the native tool output. The trick is whether the library API is good enough. So if you want to win people over, just make sure it gets adopted throughout other tools. :) -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomiwUWHWYLdLcQAnp7QBmvQR2wfPoCy=eie-jrvyw0HfA>