From owner-freebsd-current@freebsd.org Sun Nov 15 18:09:38 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 91725A2F6A5 for ; Sun, 15 Nov 2015 18:09:38 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 562321782 for ; Sun, 15 Nov 2015 18:09:37 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 62FA3DC07 for ; Sun, 15 Nov 2015 18:09:37 +0000 (UTC) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? To: freebsd-current@freebsd.org 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> From: Allan Jude Message-ID: <5648CA60.3060800@freebsd.org> Date: Sun, 15 Nov 2015 13:09:36 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <6EDFB74B-2206-46E7-85F7-8DE05FB6D325@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9cBls7lfNEjNBwMboC9donM9edpOWpuND" 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:09:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9cBls7lfNEjNBwMboC9donM9edpOWpuND Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-15 13:06, Garrett Cooper wrote: >=20 >> On Nov 15, 2015, at 09:51, Andrey Chernov wrote: >> >>> On 15.11.2015 20:37, Adrian Chadd wrote: >>>> On 15 November 2015 at 09:10, Dan Partelly w= rote: >>>> Meaning, is that simple to push things in head , if somone does the = work, even with with no proper review of the problem at hand , and the pr= oposed solutions ? >>> >>> Nope and yup. The juniper folk had a solution to a problem multiple >>> people had requested work on, and their proposal was by far the >>> furthest along code and use wise. >>> >>> It's all fine and good making technical decisions based on drawings >>> and handwaving and philosophizing, but at some point someone has to d= o >>> the code. Juniper's libxo was the furthest along in implementation an= d >>> production. >> >> It seems it is the only and final argument for libXO existence. I >> remember 2 or 3 discussions against libXO spontaneously happens in the= >> FreeBSD lists, all ended with that, approximately: "we already have th= e >> code and you have just speculations". Alternative and more architectur= e >> clean ideas, like making standalone template-oriented parser probably >> based on liXO, are never seriously considered, because nobody will cod= e >> it, not for other reasons. >=20 > We lack a [dtd/json] spec for tools, so programming for xo'ification do= esn't seems like the best idea in the world to me from a end-user sysadmi= n/developer perspective. >=20 > I could just as easily use standard tools like awk, grep, sed, and more= advanced languages like perl or Python to parse output, and assuming out= put doesn't get a major rewrite, I'd just go with that method that's work= ed pretty well for me over the last 10 years of my career.. >=20 > Cheers, > -NGie > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 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 wil= l. --=20 Allan Jude --9cBls7lfNEjNBwMboC9donM9edpOWpuND Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWSMpgAAoJEBmVNT4SmAt+R+8P/jLkL4Y9NkIgytzgXssxSDj0 W+dI8jCdVbzO3T5SxPBGkIpACa+wihQ1Ockq/ABonFdJd7+dxNts6TpSB3OJe/AV Ug5apEWJIDPElTHCODAj1UBHPIXfBriZhumuFHj99olGT7k9sD8sQNpF7hkFazPi ftfIBLLv9ZS/cquFW76wO1mdhggpu2vtLOv5GaDvrOzNfeP2xgmuBc9ZaU32mylf 1ub9ySoPuuc54/KL/eLwPUFQTbFVODJMaysGXub4/DRgw5R8/sjp4QQUo3LR7cI0 BcAAvMI1M5QAbkXNoAhWw/lNEynH8kTsiATwOa/zp2xmLGBLC0yQfVTsK6YIJNaS kLEVbDJ1AbUJzvzpATOv7IB4UUDUsjxgtTTrrddL9uJhf8yHesyuiFQ7WhKVnkqE HoBxxhigVNEr+0eXbhLxeoBtDaX93pnJjU8irCkxDY1E9P5RRepI9Bxy2KunT9Ff 7uClcNORU6c2WSCsLUdFtBc2uB3esSgsIs2I1XPKJhGHZjwXwTy2pX77nSbhpe3n omE6R86X5RvGIPoVIX+48hKeO6L01uasi6Kstl8khQQjDB1bSxpxPv+04QfbjsSc sxqIZhWL+JmY99QlPnXSgiIOCve2GlAUnSRSP2jsteGeBVkzArm2tDoT7F50AJgl w8IPErRWrUK8jyf1OEfS =idqt -----END PGP SIGNATURE----- --9cBls7lfNEjNBwMboC9donM9edpOWpuND--