Date: Fri, 23 May 2014 18:45:51 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Freddie Cash <fjwcash@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: who pay for such webpages? Message-ID: <alpine.BSF.2.00.1405231845330.26057@wojtek.tensor.gdynia.pl> In-Reply-To: <CAOjFWZ7Wk2tS-NgdNnG1QsnKq=Z7_88qjx5gn3_OCK4=NJVBYA@mail.gmail.com> References: <alpine.BSF.2.00.1405231516580.24737@wojtek.tensor.gdynia.pl> <CAOjFWZ7Wk2tS-NgdNnG1QsnKq=Z7_88qjx5gn3_OCK4=NJVBYA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
just another proof of policy "test yourself, don't read opinions" On Fri, 23 May 2014, Freddie Cash wrote: > On Fri, May 23, 2014 at 6:17 AM, Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> wrote: > http://aboutthebsds.wordpress.com/ > > ?It's a known anti-BSD trolling website. Just ignore it. Don't even waste your time trying to correct anything via the comments as the site admin just deletes truthful, pro-BSD comments.? > > > -- > Freddie Cash > fjwcash@gmail.com > > From owner-freebsd-hackers@FreeBSD.ORG Fri May 23 20:45:48 2014 Return-Path: <owner-freebsd-hackers@FreeBSD.ORG> 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 A1A588C2; Fri, 23 May 2014 20:45:48 +0000 (UTC) Received: from h.highsecure.ru (h.highsecure.ru [144.76.31.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F1A624CF; Fri, 23 May 2014 20:45:47 +0000 (UTC) Received: from [172.24.172.195] (global-2-11.nat.csx.cam.ac.uk [131.111.185.11]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: vsevolod@highsecure.ru) by h.highsecure.ru (Postfix) with ESMTPSA id E5CBC300335; Fri, 23 May 2014 22:45:07 +0200 (CEST) Message-ID: <537FB374.2000800@highsecure.ru> Date: Fri, 23 May 2014 21:45:40 +0100 From: Vsevolod Stakhov <vsevolod@highsecure.ru> User-Agent: Mutt/1.5.22 (2013-10-16) MIME-Version: 1.0 To: Adrian Chadd <adrian@freebsd.org> Subject: Re: [GSoC] Machine readable output from userland utilities References: <49E9736E-AD14-4647-8B15-30603D01360C@mail.bg> <537F0DD9.6090805@highsecure.ru> <537F11A9.8020504@mu.org> <CAETOPp0k8kESHkYShksovDm04pm4as9DoAfCm2-ojJ3in=4hsw@mail.gmail.com> <CAJ-VmomBDfePkKXMf_piG+hnhmwhhTREm5a5m2Qt=7U8E585Ww@mail.gmail.com> In-Reply-To: <CAJ-VmomBDfePkKXMf_piG+hnhmwhhTREm5a5m2Qt=7U8E585Ww@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD <freebsd-hackers.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>; List-Post: <mailto:freebsd-hackers@freebsd.org> List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 23 May 2014 20:45:48 -0000 On 23.05.2014 17:04, Adrian Chadd wrote: > 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? That is actually exactly what I'm proposing by using UCL. Store output as UCL objects and convert them to a human readable output, json, xml, yaml, libnv. Moreover, libucl is already in the base, so it is worth to check if its capabilities is enough for the vast majority of userland tools. -- Vsevolod Stakhov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1405231845330.26057>