| Dixy | ron | |
|---|---|---|
| 3 | 24 | |
| 28 | 3,146 | |
| - | 2.2% | |
| 10.0 | 7.6 | |
| about 7 years ago | 16 days ago | |
| Swift | Rust | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Dixy
-
JSON vs. XML with Douglas Crockford
I remember one time designing the simplest and most readable data format ever and came up with this https://github.com/kuyawa/Dixy after removing all I could and still make it usable
I'm leaving it here because it will never be used for anything but at least it may inspire somebody design a better format with simplicity in mind
- Dixy: Data Format Based on Dictionaries
-
Internet Object – A JSON alternative data serialization format
YAML and its "Arrays" are really broken. The problem I see with Internet Object is that it's also implying this kind of mechanism.
Every time I read about new formats, they seem to get either the 1-n relations or the n-n relations implemented well, but not both. I guess that's what's so hard about map/reduce...
Regarding YAML: somebody on HN mentioned his project DIXY a couple years ago, and it's much much _much_ easier to parse than YAML. [1] I'm using this over YAML pretty much everywhere now.
[1] https://github.com/kuyawa/Dixy
ron
-
XML is better than YAML
Whenever this kind of arguments come up, I am sad that RON (https://github.com/ron-rs/ron) is not better known. To me it feels like a cleaner and better JSON.
In any case, my little experience with it had made me hate YAML. Generally speaking, I have come to dislike any language with significant whitespace other than Haskell.
-
What config format do you prefer?
Part of the reason why I migrated away from RON in system76-scheduler is because I needed to rely on the 253-untagged-enums branch from https://github.com/MomoLangenstein/ron. Which still isn't resolved today: https://github.com/ron-rs/ron/pull/451.
-
Ron: Rusty Object Notation
Serde is strongly, strictly typed: you have to specify what type you want to decode to. It’s nothing like Python’s Pickle protocol.
See, for example, https://github.com/ron-rs/ron/blob/484fcab0686dfd18c7e29b6c1..., where it (in a type-inferency way) says “parse as Config”.
- JSON vs. XML with Douglas Crockford
- Ron – Rusty Object Notation
- They're rebuilding the Death Star of complexity
What are some alternatives?
zed - Rethinking code editing.
toml.io - Source Code for toml.io
hujson - HuJSON: JSON for Humans (JWCC: JSON w/ comments and trailing commas)
json5 - JSON5 — JSON for Humans
edn - Extensible Data Notation
kdl - the kdl document language specifications
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
jsonschema-key-compression - Compress json-data based on its json-schema while still having valid json
yaml-reference-parser
zed - A novel data lake based on super-structured data
typescript-json-schema - Generate json-schema from your Typescript sources