unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: using Cuirass to track a guix packages' git
Date: Wed, 28 Sep 2016 13:59:13 +0200	[thread overview]
Message-ID: <87y42c2q26.fsf@gnu.org> (raw)
In-Reply-To: <87h995c0r2.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sat, 24 Sep 2016 07:42:09 +0200")

Jan Nieuwenhuizen <janneke@gnu.org> writes:

> Mathieu Lirzin writes:
>
>> David Craven <david@craven.ch> writes:
>>
>>> I think the web interface and the json API are two different
>>> "projects".
>>
>> Agreed.
>
> Oh!  Then why choose json (poor-man's-sexps?) over sexps?  I'm mostly
> just using sexps with read and write, and pipe through json translators
> when crossing the border to the javascript realm.

AIUI JSON usage is not limited to JavaScript since almost every
programming language has a parser for it.  IMO, this is its main
advantage which overcomes its technical limitations.

However if using both S-EXP and JSON is possible without adding
complexity we could provide them both throught HTTP.

-- 
Mathieu Lirzin

      reply	other threads:[~2016-09-28 11:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 22:10 using Cuirass to track a guix packages' git Jan Nieuwenhuizen
2016-09-20 19:49 ` Mathieu Lirzin
2016-09-22 22:03 ` Mathieu Lirzin
2016-09-23 13:11   ` Jan Nieuwenhuizen
2016-09-23 13:44     ` Jan Nieuwenhuizen
2016-09-23 15:25     ` Mathieu Lirzin
2016-09-23 15:39       ` Jan Nieuwenhuizen
2016-09-23 17:59         ` Mathieu Lirzin
2016-09-23 19:05           ` Jan Nieuwenhuizen
2016-09-23 22:36             ` Mathieu Lirzin
2016-09-23 22:43               ` David Craven
2016-09-23 22:59                 ` Mathieu Lirzin
2016-09-24  5:42                   ` Jan Nieuwenhuizen
2016-09-28 11:59                     ` Mathieu Lirzin [this message]

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y42c2q26.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.org \
    /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://git.savannah.gnu.org/cgit/guix.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).