From: Jeff Hostetler <git@jeffhostetler.com>
To: Jacob Keller <jacob.keller@gmail.com>, Jeff King <peff@peff.net>
Cc: Git mailing list <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
lars.schneider@autodesk.com,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH 0/2] routines to generate JSON data
Date: Mon, 19 Mar 2018 13:31:50 -0400 [thread overview]
Message-ID: <d814130f-dce7-4513-02a5-469c97464715@jeffhostetler.com> (raw)
In-Reply-To: <CA+P7+xpGWZaFMWhN72beUVaV_HuECAAEYhf+UT-CPZUV+Gew4Q@mail.gmail.com>
On 3/17/2018 3:38 AM, Jacob Keller wrote:
> On Fri, Mar 16, 2018 at 2:18 PM, Jeff King <peff@peff.net> wrote:
>> 3. Some other similar format. YAML comes to mind. Last time I looked
>> (quite a while ago), it seemed insanely complex, but I think you
>> could implement only a reasonable subset. OTOH, I think the tools
>> ecosystem for parsing JSON (e.g., jq) is much better.
>>
>
> I would personally avoid YAML. It's "easier" for humans to read/parse,
> but honestly JSON is already simple enough and anyone who writes C or
> javascript can likely parse and hand-write JSON anyways. YAML lacks
> built-in parsers for most languages, where as many scripting languages
> already have JSON parsing built in, or have more easily attainable
> libraries available. In contrast, the YAML libraries are much more
> complex and less likely to be available.
>
> That's just my own experience at $dayjob though.
Agreed. I just looked at the spec for it and I think it would be
harder for us to be assured we are generating valid output with
leading whitespace being significant (without a lot more inspection
of the strings being passed down to us).
Jeff
next prev parent reply other threads:[~2018-03-19 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 19:40 [PATCH 0/2] routines to generate JSON data git
2018-03-16 19:40 ` [PATCH 1/2] json_writer: new routines to create data in JSON format git
2018-03-16 19:40 ` [PATCH 2/2] json-writer: unit test git
2018-03-16 21:18 ` [PATCH 0/2] routines to generate JSON data Jeff King
2018-03-16 23:00 ` Ævar Arnfjörð Bjarmason
2018-03-20 5:52 ` Jeff King
2018-03-17 7:38 ` Jacob Keller
2018-03-19 17:31 ` Jeff Hostetler [this message]
2018-03-19 10:19 ` Jeff Hostetler
2018-03-20 5:42 ` Jeff King
2018-03-20 16:44 ` Jeff Hostetler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d814130f-dce7-4513-02a5-469c97464715@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=jeffhost@microsoft.com \
--cc=lars.schneider@autodesk.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).