Re: [Json] Human JSON (Hjson)

Carsten Bormann <> Tue, 24 May 2016 23:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E69F12D5D3 for <>; Tue, 24 May 2016 16:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lzbgc5BVCasJ for <>; Tue, 24 May 2016 16:52:17 -0700 (PDT)
Received: from ( [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 69CEE12D5D5 for <>; Tue, 24 May 2016 16:52:17 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F3B2FC5A4F; Wed, 25 May 2016 01:52:15 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at
Received: from ([IPv6:::ffff:]) by ( [::ffff:]) (amavisd-new, port 10024) with ESMTP id hZCRz8WrkHkf; Wed, 25 May 2016 01:52:14 +0200 (CEST)
Received: from nar-3.local ( []) (Authenticated sender: by (Postfix) with ESMTPSA id D6C1CC5A46; Wed, 25 May 2016 01:52:13 +0200 (CEST)
Message-ID: <>
Date: Wed, 25 May 2016 01:52:11 +0200
From: Carsten Bormann <>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Christian Zangl <>
References: <>
In-Reply-To: <>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [Json] Human JSON (Hjson)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.


> 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