From owner-freebsd-current@freebsd.org Sun Nov 15 18:14:26 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF7C6A2FA90 for ; Sun, 15 Nov 2015 18:14:26 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7E881DDA; Sun, 15 Nov 2015 18:14:26 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by igcph11 with SMTP id ph11so44536759igc.1; Sun, 15 Nov 2015 10:14:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=O4APO9nBJHx4hch0c4KeZquIVzLEt9jAWUdE5vRA8PQ=; b=waTOg5ykeQjk440FmVU4ua1mwYTKVNaJQA7TzK2HiwyyKHAFROhW0kN9XYAxY9Uywm W+xW/i/1NPUtRJOFDa+kzUF3vzW5qHBKWy3+7VtLIglZ/yc9OEIE94QxIOMFLuOar5xu YNLe/5aJGHcqZBwrpTKAos1WUdRUCGAgLzTEVQQM1CLmOh19k4HFmki/SOxZl2WWpaMG ZUnCZsjvID7Ul5/vM5f8m0YEypdNwkLGPhsoyPF3DH9oft7QfX4+1roOoFhOsVIKJrnA emVsNaSQcM+0758wTQkOZyAcZkK3KOEPpmNGhAJ+pLq4rD5bsK1cM904FnAYKkftR0xp iRAw== X-Received: by 10.50.49.109 with SMTP id t13mr13118592ign.89.1447611266059; Sun, 15 Nov 2015 10:14:26 -0800 (PST) Received: from [192.168.20.11] (c-24-16-212-205.hsd1.wa.comcast.net. [24.16.212.205]) by smtp.gmail.com with ESMTPSA id 26sm7567380iod.9.2015.11.15.10.14.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Nov 2015 10:14:24 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? From: Garrett Cooper X-Mailer: iPhone Mail (13B143) In-Reply-To: <5648CA60.3060800@freebsd.org> Date: Sun, 15 Nov 2015 10:14:23 -0800 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro> <5648C60B.6060205@freebsd.org> <6EDFB74B-2206-46E7-85F7-8DE05FB6D325@gmail.com> <5648CA60.3060800@freebsd.org> To: Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 18:14:27 -0000 > On Nov 15, 2015, at 10:09, Allan Jude wrote: ... > The big difference is, a json parser isn't going to blow up if a new > field gets added in the middle, and your awk/grep/sed script probably will= . That's a plus to those formats, yes, but if someone changes the field name (= which can happen today, on a whim, and would go unnoticed for a while becaus= e no tests/spec), you'll run into a KeyError in Python or an equivalent erro= r message in your language of choice. Thanks,=