4 ms·
Almost all of the issues solved by JSON5, are also solved by EDN: https://github.com/edn-format/edn https://github.com/edn-format/edn I'd like to see a little
by berdario 13y ago
Almost all of the issues solved by JSON5, are also solved by EDN:
https://github.com/edn-format/edn https://github.com/edn-format/edn
I'd like to see a little bit more love for edn... and if you're gonna pick something incompatible with plain old JSON, why not edn?
- captainmuon 13y agoI can only speak for myself, but I don't want something incompatible with JSON, or completely different. I want a format that looks like Javascript or Python code, and that is a strict superset of JSON (e.g. can parse all valid JSON). I want to pluck my object or list literal from my Python or JS code, put it into a config file, and have it work, no matter wheter I have final commas in lists or not. I want to be able to insert comments. And I want to be able to describe it as "JSON, but you can use comments", so people will be able to understand it immediately and edit the files. This is similar to what Sublime Text uses for its config files, for example. EDN, or more prominently YAML are just not well-known enough (and the latter is hellishly complicated). Also, a nicety of JSON5 is that it serializes into plain JSON, so interopability is always ensured.