Re: YAML Was: CommitFest status/management
Ron Mayer <rm_pg@cheapcomplexdevices.com>
From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Dimitri Fontaine <dfontaine@hi-media.com>, Robert Haas <robertmhaas@gmail.com>, Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>, Josh Berkus <josh@agliodbs.com>, Tom Lane <tgl@sss.pgh.pa.us>, Ron Mayer <rm_pg@cheapcomplexdevices.com>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@postgresql.org
Date: 2009-12-07T16:42:43Z
Lists: pgsql-hackers
Greg Smith wrote: > That's a step backwards. By providing JSON format, we've also satisfied > people who want YAML. Ripping out JSON would mean we *only* support > YAML. There are far many more JSON parsers than YAML parsers, which is > why I thought the current code committed was good enough. XML parsers are common enough IMHO the other computer readable formats can't be that important from a computer-readability perspective, leaving their main benefit as being human friendly. I like YAML output; but I think the most compelling arguments against the patch are that if so many people want different formats it may be a good use case for external modules. And far more than yaml output, I'd like to see a flexible module system with an equivalent of "cpan install yaml" or "gem install yaml". I suppose one could argue that instead of YAML we design a different human-oriented format for loosely structured data; but that seems even harder.