Re: YAML 2.0: drop arbitrary nodes to be used as keys

On Wed, Mar 2, 2016 at 5:56 AM, Osamu TAKEUCHI <[email protected]> wrote:
> Dear Andrey,
>
> In YAML 1.2, the spec says "In contrast (to JASON), YAML’s
> foremost design goals are human readability and support
> for serializing arbitrary native data structures."
>
> If YAML 2.0 ceases to be a native data serialization
> language, people will just continue to use YAML 1.2 for
> the purpose. Then, it is desirable to continue
> maintaining YAML 1.2 in parallel with YAML 2.0.
>
> Another point: it is repeatedly discussed in this list
> that *inter-operability* across specific applications
> is not so important. Every YAML file has its own purpose.

I'm not nearly as invested in YAML as you guys, and don't have a
strong opinion against complex keys.  However, I would very much like
to be able to advocate for use of YAML instead of JSON in a project I
work on.  I feel this way because I've not enjoyed all the noise and
bad not-human-friendly parser behavior when using JSON.  For me to be
able to do this though interoperability is an issue.  It doesn't need
to be all YAML as long as the interoperable subset is totally clear,
and the path to JSON likewise.  Sounds like some good things are being
considered and maybe YAML is still a realistic choice afterall.

Britton

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core