Re: [Json] What is a JSON-text? [REVISITED]

[Nico Williams <[e-mail]>]

On Thu, Oct 3, 2013 at 1:24 PM, Nico Williams <[e-mail]> wrote:
> Because JSON isn't always used to transport values across networks
> (where it'd be silly to send scalar values with all the overheade of
> HTTP and TCP/IP, say).  JSON is often used for interop between local
> components, where the overhead that would make laughable the use of
> scalar values at the top-level just doesn't apply.  E.g., the Python
> bindings to libjq.  Indeed, here your suggestion that I call "lame"
> *adds* undesirable overhead.

I should add that the overhead is also developer overhead: having to
create the array/object to contain the solitary scalar value, then
destructure it to get it back.

I don't care if you have two JSON text definitions (see previous post)
or just allow all value types at the top-level.  It's the same to me,
as long as parser implementors know to provide the option for it (if
they don't just bleeping allow all value types at the top-level
outright, no option necessary, especially so for those implementations
that use run-time typing, which includes several C implementations,
FYI).

Nico
--