native json parsing

[senordhuff]

Hi,

I've asked about this before but I'm just double-checking and clarifying 2 points.

1. Setting useStrictJSON to true will force our application to use the brower's native json.parse instead of eval, correct? The docs don't specify this but I believe that is true.

2. Is there no meaningful performance difference between eval and json.parse for most browsers? This thread suggests there is a difference for Chrome as an example but I'm not sure if it is significant enough that it would be a noticeable performance improvement: http://forums.smartclient.com/showthread.php?t=21810&highlight=json.parse

[Isomorphic]

JSON parsing vs eval is not the only thing that is done to inbound data. Because of the way JSON parsing works, bits of data such as date and time values need to be processed after JSON parsing, whereas this is avoided with eval().

Big picture: don't try to tweak this for performance reasons, leave the right setting to the framework.