Hacker News Reader

If we’re going to extend JSON I don’t see the point unless we decide on a standard date interchange format that can be validated.

Not a strong with some format in it but an actual date format.

I know this is probably a problem because there are no date literals in JS, but it’s my #1 complaint about JSON.

I don’t care about trailing commas. Identifiers for names instead of quoted strings would be nice.

But I want a date format.

View on HN

Literally the only things actually "wrong" with JSON (as opposed to complaints about developer ergonomics) are the lack of proper support for floating point special values (e.g., +inf, -inf, nan) and not having a date literal (RFC3339 would be ideal).

Maaaaaaybe removing tolerance of duplicate keys.

Possibly, a binary literal (hex64 bytestring, maybe like << base64 encoded>>) syntax.

Reply on news.ycombinator.com