Date: Mon, 9 Dec 2013 15:43:44 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: "freebsd-stable@freebsd.org Stable" <freebsd-stable@freebsd.org> Cc: Alfred Perlstein <bright@mu.org> Subject: Re: BIND segway -> python -> first-class ports Message-ID: <8D54491D-5A1C-4D30-AD48-12336D0726DC@gsoft.com.au> In-Reply-To: <52A51438.4090200@bluerosetech.com> References: <mailman.313.1386119137.1390.freebsd-stable@freebsd.org> <529E8C53.6020208@freebsd.org> <Pine.GSO.4.64.1312032238220.15897@sea.ntplx.net> <20131204060246.GV2951@home.opsec.eu> <CAN6yY1udd1GbQVK4YR-yxNe7vqX3S1refQwch2cafRnMv=W4mA@mail.gmail.com> <CAFHbX1K1AgZ4FaEjP_vvnfiwDWsj6M3ysEVn4taX_4_p%2B1Z8Nw@mail.gmail.com> <CAN6yY1tjS=uk1Qr-sBN0PT73xpP%2BBxL8wLt9aosYfWf751rC5A@mail.gmail.com> <52A12843.3010204@freebsd.org> <0BFC927B-D72E-4926-BB3D-2C000F310BDD@fisglobal.com> <7271C4C4-7BAB-4DA7-9E10-49D5B2DB8964@mu.org> <52A51438.4090200@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Dec 2013, at 11:22, Darren Pilgrim <list_freebsd@bluerosetech.com> = wrote: > 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 beneficial? Beneficial here means otherwise impossible = functionality or automation gains without adding barriers for low-level = diagnostics, tuning, corner-case configurations and other modes of = advanced control. It is not that parsing the human readable output of the tools is = impossible, it's that it's tedious bullshit code that you shouldn't have = to write in the first place. 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` 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 :) (I don't care if it's JSON, XML or smoke signals just so long as it = isn't hideously slow). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D54491D-5A1C-4D30-AD48-12336D0726DC>