I agree with those who say JSON should never change, but should one day be replaced. It behooves us to think about what that replacement should be.
My own peeves:
* Numbers are stored in decimal but usually interpreted as binary with no guidance about rounding.
* The concatenation of valid JSON blobs is never valid JSON.
* The empty string is not valid JSON.
The last two can be "fixed" by a format called "arraySON" where the global blob represents not a JSON object (dictionary), but the contents of an array plus an optional trailing comma.
Or given some of the ideas on this thread, perhaps a manadatory leading comma.
replies(2):