All I want is a datetime literal: #2018/01/31 17:00:21.2234233#.
I don't even care that it isn't backwards compatible. Eventually platforms will catch up... so the sooner it's added the sooner everything will catch up.
Is that because you want date/times in JSON? Shouldn't it include a timezone, and maybe implement ISO8601?
Putting it into ES won’t change the JSON standard though.
Wouldn't it have to? It does stand for JavaScript Object Notation after all.
That's where the idea came from. But it's now a completely standalone standard, with its own grammar, that just happens to be compatible with a subset of ES.
Even that's not technically true. You can represent things in JSON that can't be represented in ES object literals. There's a proposal in Stage 3 to fix that though: https://github.com/tc39/proposal-json-superset