@spicyj I agree that recklessly paving natives is no good and can cause problems, but JSON3 is trying rather hard to not pave them (note that it doesn't even ex

@spicyj I agree that recklessly paving natives is no good and can cause problems, but JSON3 is trying rather hard to not pave them (note that it doesn't even extend Date.prototype), and only paves parse/stringify when fixing broken implementations that are not cross-browser consistent or spec-compliant. With the fix in place it means the API will produce consistent output cross-browser which is a good thing.