Hacker News Reader

Comment by viraptor | Hacker News Reader

Json has a perfectly fine order preserving key-value map:

    [["Key1", "value1"], ["key2", ...

You just need to deserialise it into a specific collection on the receiver. It's within standards and there are no weird parser issues.

View on HN

That's a way. A way that, IMHO, vastly diminishes its expressive power on the reader's side, which I do not consider a very good thing. Most solutions to the issue are of this nature.

Consider serialized JSON already has a natural ordering, which is thrown away for some reason (probably parsing convenience).

> which is thrown away for some reason (probably parsing convenience).

It's got nothing to do with parsing. The json comes from JavaScript syntax, where objects represent unordered mapping. Json naturally does the same.

If you want expressive power for reading, json is very poor in comparison to pretty much everything else. Just use it for simple serialisation.

Granted, it came from there, but that was back in the days of map=eval(json) and they're gone. There is nothing in json the format (as opposed to json the language construct) to impose the unordered behavior.(Or, for that matters, the 'no comments' bit).

> There is nothing in json the format [..] to impose the unordered behavior

That's not true. The spec at http://www.json.org/ says "An object is an unordered set of name/value pairs".

Yes, that's in the specs. But what I meant is that there is nothing intrinsic to the format demanding unordered behavior.

Reply on news.ycombinator.com