ron
| yaml-reference-parser | ron | |
|---|---|---|
| 1 | 24 | |
| 33 | 3,135 | |
| - | 1.8% | |
| 0.0 | 7.6 | |
| 11 months ago | 24 days ago | |
| CoffeeScript | 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.
yaml-reference-parser
-
YAML: It's Time to Move On
> There's no canonical YAML implementation
The formal grammar counts as canonical and several implementations are derived from it: https://github.com/yaml/yaml-reference-parser
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?
starlark - Starlark Language
toml.io - Source Code for toml.io
typescript-json-schema - Generate json-schema from your Typescript sources
json5 - JSON5 — JSON for Humans
nestedtext - Human readable and writable data interchange format
kdl - the kdl document language specifications
openapi-python-client - Generate modern Python clients from OpenAPI
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
cue - CUE has moved to https://github.com/cue-lang/cue
yamllint - A linter for YAML files.