On 15 February 2016 at 00:37, Patrick Lauer <[email protected]> wrote:
> Or JSON, or YAML, or whatever
> is trendy now.
I would love a JSON form. I tried doing my own stuff with XML and I
gave up in the complexity factory I found myself building around it :(
Just ... not YAML. The YAML spec is much less well defined and much
less "regular", and much less ubiquitous as a transport.
And if you standardize on JSON, JSON is valid YAML 1.2, but not vice versa.
And so as long as you don't do any cute things like permit different
structures in the same slots like:
{ author => "[email protected]" }
{ author => { email => "[email protected]" , name => ... }}
You'll be fine, Because you get nice messes when code expects a value
to be a hash instead of a scalar and try to keep the data
self-consistent. Its just not worth the programming expense in every
single implementation just to provide a little sugar syntax.
--
Kent
KENTNL - https://metacpan.org/author/KENTNL
