From owner-freebsd-arch@FreeBSD.ORG Tue Jul 29 04:49:17 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B8A13D7 for ; Tue, 29 Jul 2014 04:49:17 +0000 (UTC) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44EAF22C2 for ; Tue, 29 Jul 2014 04:49:16 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 6FFF77C7D9; Mon, 28 Jul 2014 21:49:15 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 25929-10; Mon, 28 Jul 2014 21:49:15 -0700 (PDT) Received: from [10.8.0.10] (unknown [10.8.0.10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 28D937C7D6; Mon, 28 Jul 2014 21:49:13 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML From: Jordan Hubbard In-Reply-To: Date: Mon, 28 Jul 2014 21:49:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> To: Jos Backus X-Mailer: Apple Mail (2.1878.6) Cc: arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2014 04:49:17 -0000 On Jul 27, 2014, at 11:06 PM, Jos Backus wrote: > It would be great if libyaml and libucl would converge, but instead = it's > likely that the number of solutions trying to solve the same problem = will > continue to proliferate, and we are stuck with more and more = configuration > file formats :-( I=92m a huge fan of unified data formats; Apple picked XML and the plist = DTD a long time ago, a decision which has worked rather nicely in = practice, but I=92m more in love with the unification that produced than = I am in love with XML itself. That said, it seems like this late push = for YAML is a similar case for divergence just because=85erm=85 you = don=92t like JSON? It seems like libucl has basically backed JSON with = the addition of a little syntactic sugar, so what=92s wrong with that? Is there some reason JSON is not sufficient? I think that=92s a better = question to ask, since the conversation otherwise quickly tends to sound = a little like =93I=92ll accept any single unified format as long as it=92s= the specific one I like!=94 :) I think the greater good argument = would suggest just picking one that=92s expressive enough (roll a pair = of dice), put on your bikeshed-proof sunglasses, and proceed. - Jordan