From owner-freebsd-stable@FreeBSD.ORG Mon Dec 9 11:52:05 2013 Return-Path: Delivered-To: freebsd-stable@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 33C54AE6 for ; Mon, 9 Dec 2013 11:52:05 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 18C0312FE for ; Mon, 9 Dec 2013 11:52:04 +0000 (UTC) Received: from [10.0.1.108] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 05D861A3C19; Mon, 9 Dec 2013 03:52:02 -0800 (PST) References: <529E8C53.6020208@freebsd.org> <20131204060246.GV2951@home.opsec.eu> <52A12843.3010204@freebsd.org> <0BFC927B-D72E-4926-BB3D-2C000F310BDD@fisglobal.com> <7271C4C4-7BAB-4DA7-9E10-49D5B2DB8964@mu.org> <52A51438.4090200@bluerosetech.com> <8D54491D-5A1C-4D30-AD48-12336D0726DC@gsoft.com.au> Mime-Version: 1.0 (1.0) In-Reply-To: <8D54491D-5A1C-4D30-AD48-12336D0726DC@gsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11B554a) From: Alfred Perlstein Subject: Re: BIND segway -> python -> first-class ports Date: Mon, 9 Dec 2013 03:51:58 -0800 To: Daniel O'Connor Cc: "freebsd-stable@freebsd.org Stable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 11:52:05 -0000 > On Dec 8, 2013, at 9:13 PM, "Daniel O'Connor" wrot= e: >=20 >=20 >> On 9 Dec 2013, at 11:22, Darren Pilgrim w= rote: >>=20 >>> On 12/8/2013 11:02 AM, Alfred Perlstein wrote: >>> So if I were going to task the talented Devin Teske with something, >>> remember you just asked my opinion, then it would be to look at >>> putting Lua in the boot loader, getting python into base, or working >>> on making our utilities be able to output standard machine readable >>> formats such as yaml, XML and json. >>=20 >> Can you cite a real-world example of a general-purpose OS where this was b= eneficial? Beneficial here means otherwise impossible functionality or auto= mation gains without adding barriers for low-level diagnostics, tuning, corn= er-case configurations and other modes of advanced control. >=20 > It is not that parsing the human readable output of the tools is impossibl= e, it's that it's tedious bullshit code that you shouldn't have to write in t= he first place. >=20 > I would kill for a way to be able to do something like.. > output=3D`somecmd -J` > foo=3D`jsonextract -f some.field $output` > bar=3D`jsonextract -f another.field.here $output` >=20 > Even nicer would be if the shell could do it internally so you didn't have= to re-parse it all the time but it's a start :) >=20 > (I don't care if it's JSON, XML or smoke signals just so long as it isn't h= ideously slow). >=20 You have described exactly what we are trying to accomplish. Thank you!