IETF Logo Mail Archive

Re: [Json] Human JSON (Hjson)

Carsten Bormann <cabo@tzi.org> Tue, 24 May 2016 23:52 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E69F12D5D3 for <json@ietfa.amsl.com>; Tue, 24 May 2016 16:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzbgc5BVCasJ for <json@ietfa.amsl.com>; Tue, 24 May 2016 16:52:17 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69CEE12D5D5 for <json@ietf.org>; Tue, 24 May 2016 16:52:17 -0700 (PDT)
Received: from mfilter33-d.gandi.net (mfilter33-d.gandi.net [217.70.178.164]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id F3B2FC5A4F; Wed, 25 May 2016 01:52:15 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter33-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter33-d.gandi.net (mfilter33-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id hZCRz8WrkHkf; Wed, 25 May 2016 01:52:14 +0200 (CEST)
X-Originating-IP: 93.199.242.26
Received: from nar-3.local (p5DC7F21A.dip0.t-ipconnect.de [93.199.242.26]) (Authenticated sender: cabo@cabo.im) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id D6C1CC5A46; Wed, 25 May 2016 01:52:13 +0200 (CEST)
Message-ID: <5744E92B.3010704@tzi.org>
Date: Wed, 25 May 2016 01:52:11 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Christian Zangl <coralllama@gmail.com>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com>
In-Reply-To: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/sXEKwLFgH4W78cvA_AHGCUMGzos>
Cc: json@ietf.org
Subject: Re: [Json] Human JSON (Hjson)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 23:52:19 -0000

First, the name. If something calls itself X, it should be an X.

HJSON is not JSON.  It is a Hacked JSON.

Second,

> People seem to prefer JSON for
> configuration over YAML and other config formats.

Can't be.  YAML *contains* JSON.
If you like JSON, you already like YAML, because every JSON file is a
YAML file.
(You may not like what else YAML brings to the table, but that would be
a mistake.)

(If you like JSON mostly because everything is JSON, well: HJSON isn't.)

Third, YAML also isn't stuck with the limitations of the JSON data model.
Binary data, maps with keys that aren't strings, etc.

I'm not opposed to writing a spec for a Hacked JSON.  However, I think
the time spent for doing that would be much better invested in an
updated spec for YAML.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email