From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 22:11:22 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5000B946; Sun, 25 May 2014 22:11:22 +0000 (UTC) Received: from udns.ultimateDNS.NET (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6DCC28CD; Sun, 25 May 2014 22:11:20 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id s4PLxtKt025071; Sun, 25 May 2014 15:00:01 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id s4PLxoKS025058; Sun, 25 May 2014 14:59:50 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net ([209.180.214.225]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Sun, 25 May 2014 14:59:50 -0700 (PDT) Message-ID: In-Reply-To: References: <49E9736E-AD14-4647-8B15-30603D01360C@mail.bg> <537F0DD9.6090805@highsecure.ru> <537F11A9.8020504@mu.org> Date: Sun, 25 May 2014 14:59:50 -0700 (PDT) Subject: Re: [GSoC] Machine readable output from userland utilities From: "Chris H" To: "Adrian Chadd" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Alfred Perlstein , FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 May 2014 22:11:22 -0000 > Hey all, > > I'd actually prefer that some library API (like what's in libstatfoo) > gets fleshed out to cover what hooks and options are required so you > don't have to have the bikeshed argument of "what format." You only > need to write some code to output it in the format you want. > > The UNIX way is tools, not policy. The library is a policy, sure, but > it's a policy to let you define your own policies. It won't be locking > anyone into anything like "json or bust." > > So how about the focus be on that, rather than trying to teach > individual tools about individual encoding types? > +1 ...and thanks for mentioning it. :) > > > -a > > > On 23 May 2014 08:38, Jos Backus wrote: >> On May 23, 2014 2:15 AM, "Alfred Perlstein" wrote >>>point to note is that the intent is to have an output that is very >> consumable by modern scripting languages and modules. That would very >> likely be JSON output. >>> >>> -Alfred >> >> I'd actually prefer YAML output. YAML is a much more expressive superset of >> JSON (YAML parsers can read JSON), but given that VHS beat out BetaMax, I >> fully expect JSON to win, and YAML to fade into oblivion. Sad. >> >> Jos >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >