Re: [GSoC] Machine readable output from userland utilities

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?

-a

On 23 May 2014 08:38, Jos Backus <jos@catnook.com> wrote:
> On May 23, 2014 2:15 AM, "Alfred Perlstein" <bright@mu.org> 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"