and I argue with your conclusion.
> That doesn't make a lot of sense, as UTC does have leap seconds. Pedantic much? Posting in technical forums is such a bother. People pick at any unimportant detail. Reworded just for you: The only reliable time stamp…
I've written a few JSON parsers over the years that treat commas as whitespace. The grammar is simpler and the parser is faster as result. As long as one always emits standards-compliant JSON there's no problem. Had the…
MessagePack is better supported than UBJSON and has far more implementations in almost every language. http://msgpack.org/index.html JSON Schema draft 4 is the defacto schema standard for JSON.…
Timestamps are so complicated once you factor in timezones and daylight savings that it doesn't belong in JSON. Time zones are not static. They can change from country to country, or even states within countries. Ditto…
and I argue with your conclusion.
> That doesn't make a lot of sense, as UTC does have leap seconds. Pedantic much? Posting in technical forums is such a bother. People pick at any unimportant detail. Reworded just for you: The only reliable time stamp…
I've written a few JSON parsers over the years that treat commas as whitespace. The grammar is simpler and the parser is faster as result. As long as one always emits standards-compliant JSON there's no problem. Had the…
MessagePack is better supported than UBJSON and has far more implementations in almost every language. http://msgpack.org/index.html JSON Schema draft 4 is the defacto schema standard for JSON.…
Timestamps are so complicated once you factor in timezones and daylight savings that it doesn't belong in JSON. Time zones are not static. They can change from country to country, or even states within countries. Ditto…