Thank you for introducing github.com/nd-02110114/ba… Feedback is welcome from everyone 👍

Thank you for creating the plugin!

Is there a jsperf (or similar repro) for that? Tried with ±200kb serialised redux state from real APP and JSON.parse appeared to be a bit (20% to none) slower. Also does this trick make sense when all the keys in object literal are quoted?

Did you watch the video? We point to the benchmark on GitHub around the 04:58 mark: youtube.com/watch?v=ff4fgQ…

i tried a couple of time with my 2.8 megs json object did not manage to see an improvement in my flame graph. Every time someone tweets this i go and try again.

How are you measuring this exactly? Have you tried running our benchmark with your data?

That's Nice! Could I benefit of this on node/express receiving a massive payload in a post?

I may be wrong but the payload from a request is already a string and express apps are probably just json-parsing it. So you are already done.

Does this JSON.parse optimization offer any benefit once code caching kicks in? It seems to reduce the large parse cost in favour of slightly greater execution cost. But when code caching, JS parsing is almost free, whereas execution cost still matters.

Did you see the benchmark referenced in the talk? It includes warm load tests: github.com/GoogleChromeLa… cc @leszekswirski @tverwaes for code caching insights specifically