Date: Mon, 28 Jul 2014 22:56:38 -0700 From: Stephen Hurd <shurd@FreeBSD.org> To: Jordan Hubbard <jkh@mail.turbofuzz.com>, Jos Backus <jos@catnook.com> Cc: arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <53D73796.9060102@FreeBSD.org> In-Reply-To: <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.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>
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan Hubbard wrote: > Is there some reason JSON is not sufficient? I think that’s a better question to ask, since the conversation otherwise quickly tends to sound a little like “I’ll accept any single unified format as long as it’s the specific one I like!” :) I think the greater good argument would suggest just picking one that’s expressive enough (roll a pair of dice), put on your bikeshed-proof sunglasses, and proceed. The biggest problem I tend to have with JSON is that there is no comment format. I rarely update a configuration without adding a comment regarding it, and since JSON doesn't have comments, it's simply a non-starter for most of my usage. The whole "just a key that you know isn't real" hack is terrible.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D73796.9060102>