Re: [Json] On flat vs nested JSON encoding style

[Anders Rundgren <[e-mail]>]

On 2016-02-05 15:01, Phillip Hallam-Baker wrote:
<snip>
> What you are arguing for is that you want to write your structures like this
>
> struct fred { int a, int b, int c}
>
> { "a" : 1, "b" : 2, "type" : "fred", "c" : 3}
>
> Now you might think that is a reasonable way to present the data in a
> spec but most of us would say that it is hard to follow. The important
> information of the type of the structure is buried in the
> serialization stream.

I fully buy into the efficiency aspect of the nested encoding style (which I
honestly had never thought of), but when it comes to "hard to follow", predictable
serialization a la ES6 seems like a more universal solution since this also sucks:
   {
      "city": "Paris",
      "name": "John Doe",
      "country": "FR",
      "zip": 245333
   }

ES6 serialization and the nested encoding style scheme can easily be combined,
hopefully bringing out the best of both worlds!

Anders