News for hackers. Stuff that matters.
Re:JSON Support in SQL Server 2016 by rpedela on Tuesday May 19, 2015 @09:58AM (#9570041)
JSON is an improvement overall even though there are certainly issues. It is easier to read, easier to parse, and usually fewer bytes for the same data. Validation schema can be provided by JSON Schema [1]. The lack of date type and comments is annoying, but not that big of a deal. I think parsing and reading are far more important to get right which XML didn't.

1. http://json-schema.org/

Re:JSON Support in SQL Server 2016 by WorldWideWayne on Tuesday May 19, 2015 @10:46AM (#9570402)
> but not that big of a deal. I think parsing and reading are far more important to get right which XML didn't.

...in your opinion, for your use cases. I think XML is eminently more readable due to the fact that it has named types and also because I never have to read the following and figure out what goes where:

    }}}}}]]}}]]}}
JSON is great for sending data to Javascript though and I'm pretty sure that's the only reason anyone is using it.
Re:JSON Support in SQL Server 2016 by rpedela on Tuesday May 19, 2015 @11:36AM (#9570886)
You have the same problem in XML with that amount of nesting. Then you pretty print the XML or JSON and problem solved.