IETF Logo Mail Archive

Re: [Json] Human JSON (Hjson)

Christian Zangl <coralllama@gmail.com> Wed, 25 May 2016 21:42 UTC

Return-Path: <coralllama@gmail.com>
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 1635512DD84 for <json@ietfa.amsl.com>; Wed, 25 May 2016 14:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 y0MqECV6qhPW for <json@ietfa.amsl.com>; Wed, 25 May 2016 14:42:56 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 979C912D1E2 for <json@ietf.org>; Wed, 25 May 2016 14:42:56 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id n129so77625291wmn.1 for <json@ietf.org>; Wed, 25 May 2016 14:42:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dVqyh/IddqfgOwE6QoscyNdyjisfcEPTL/OcM9surks=; b=toEGyXzhJWbCNNMFhdBlUZXqIDUMfhT8z3UHdDm5IL7wbR1eS9uDrkQO74bESC+stN Rnqr+cS1kUAnt2cMUgLeXJZVispwlgEMavdngk2Gp0smMqhxlep3xtOX1DSTPwXPOm/6 /4bJAEMqihl1qyGYO2IUuMK2FzoIxou/IQkSFcVErbCDAH5novXK1wnInDDehfSVLXNZ n4JiEKvoVeWPq13VCFhDtZ2AI4LSfxYNgADcrGDtnRTIluZR93v4IUelwS3px34A0kdm 7FPD4gfw+EFvcCQ2KTXAkYOND1abwl4CambyUsoRbzzv51K3oEgkwNtwKVWIXmu+54hJ udmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dVqyh/IddqfgOwE6QoscyNdyjisfcEPTL/OcM9surks=; b=nEGkbjjVhPsvrwXYVRglrPc96PK0yFwfwgBH3o110Rkk53xLTsBOoEaKOJiVm8ScXs 9REgK10IBIwY/JMH3kv9nbGK6rqQyCTOd9us0OCj6LjT8NTv2d6Rq/0n7hR7K6AxhPvv eGYFMScHuiwpmB+zjZLu0PNi2aTiajj+afCilNS2wJobqOjPqOBf36ijA3P2DkTjO3Gx HVqHhcg+KVymSiPaeujEkGfJEhaWj1Jl3dfB1zi1D353PpOYUWmueprDd7hOgoGICHnm 6/bRBRUWf7x3T1yzUw0fpJFTuLidMr555UKVQTQpmLGfJbJVInbczBwrunbiC0RV7AYL j3VQ==
X-Gm-Message-State: ALyK8tK26d6y+5iIapOMj6IZtsvxkZ+Ea5ATvzzKvpzYBGcm5vaI/7o68Mjo718VVmJesQ==
X-Received: by 10.194.104.102 with SMTP id gd6mr736367wjb.170.1464212575005; Wed, 25 May 2016 14:42:55 -0700 (PDT)
Received: from [192.168.1.181] (178.113.72.111.wireless.dyn.drei.com. [178.113.72.111]) by smtp.googlemail.com with ESMTPSA id m7sm113415wma.10.2016.05.25.14.42.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2016 14:42:54 -0700 (PDT)
To: Carsten Bormann <cabo@tzi.org>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <5744E92B.3010704@tzi.org> <aba11a1f-d81f-b9dd-84c9-c5b16df886de@gmail.com> <57455F43.6010506@tzi.org>
From: Christian Zangl <coralllama@gmail.com>
Message-ID: <2eec2464-3315-9cd6-f850-ab83d98a94a8@gmail.com>
Date: Wed, 25 May 2016 23:42:52 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <57455F43.6010506@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/iMms6HLOZ6d-VOi5HNVEWQcTyJ4>
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: Wed, 25 May 2016 21:42:58 -0000

On 2016-05-25 10:16, Carsten Bormann wrote:
> HUMANS SHOULD NOT BE WRITING JSON *), so, no, I don't like JSON as a
> configuration file format.

Couldn't agree more!

> The people I have met who didn't know about YAML usually liked
> .ini-style **) configuration file formats, as exemplified by TOML ***).

While those are certainly better options it's not uncommon to see JSON 
configs. I'd like to get people to switch. If they switch to 
YAML/INI/TOML that's fine too. Even if you don't like the name, "Human 
JSON" signals that it's a format they already know. You can in fact just 
replace the parser and everything keeps working.

> Since my experience is that every configuration file format turns more
> and more complex over time, I prefer to base them on a powerful generic
> format such as YAML.  YAML is also pretty good in noise reduction.

JSON is such a nice format because it's easy and requires almost no 
explanation. When you look at YAML it's not easy to guess what it does 
and yaml.org only makes it worse.

-chris

v2.23.0 | Report a Bug | By Email