Please help with writing spec for async JSON APIs

joe joeedh at
Sat Aug 1 04:56:44 UTC 2015

JSON parsing is such a slow process that it motivated me to re-invent
Google Protobufs (in a nice, JS-friendly way, see ).  I never use
JSON in production code for this reason.  An async api isn't a bad idea.


On Fri, Jul 31, 2015 at 8:32 PM, Kevin Smith <zenparsing at> wrote:

> Hi Moshen,
> The semantics of your proposal are straightforward, so I don't think you
> need to provide spec text at this point.  Instead, what would be helpful is
> a quantitative analysis showing why these additional methods are needed.
> Is there any way you can demonstrate the benefit with numbers?
> On Fri, Jul 31, 2015 at 11:04 PM Mohsen Azimi <me at> wrote:
>> Hi,
>> I stumbled on lack of async APIs for JSON parsing and stringifying in
>> JavaScript a couple of weeks ago. I tried to hack
>> <> around
>> it by abusing the W3C Fetch API but that's just a hack.
>> Domenic suggested <>
>> that we should write the proposal spec for native non-blocking JSON
>> processing. I don't know what the API should look like but I made some
>> assumptions and wrote the initial spec (if I can call it spec!) and
>> published it in GitHub <>.
>> I need to learn the spec lingo and rewrite the spec in proper and
>> standard language. I need help and resources to learn the language of the
>> spec.
>> Would you please review the proposal so far (including the outstanding
>> PR)?
>> Thanks,
>> Mohsen
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at
> _______________________________________________
> es-discuss mailing list
> es-discuss at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list