awesome-json-next
ron
Our great sponsors
awesome-json-next | ron | |
---|---|---|
3 | 24 | |
55 | 3,073 | |
- | 2.1% | |
0.0 | 7.9 | |
about 3 years ago | 11 days ago | |
Rust | ||
Creative Commons Zero v1.0 Universal | 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.
awesome-json-next
-
The Norway Problem
You might look at JSON Next variants (if you remember - "classic" JSON is a subset of YAML), see https://github.com/json-next/awesome-json-next
my own little JSON Next entry / format is called JSON 1.1 or JSONX, that is, JSON with eXtensions, see https://json-next.github.io/
-
JSON with Commas and Comments
FYI: I collect JSON variants with extension at the Awesome JSON - What's Next? page [1].
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.
Sounds like RON - Rusty Object Notation
-
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
- They're rebuilding the Death Star of complexity
-
Show /r/rust: deser, an experimental serialization system for Rust
Cool project! I ran into some limitations of serde a while ago while trying to add some new features to ron: https://github.com/ron-rs/ron/pull/328. Not sure if that's the kind of issue you are planning to address, but either way it's a concrete example of a use case where serde is currently not a perfect fit.
-
YAML: It's Time to Move On
You might like RON[1]. It's far from perfect (and far from complete), but seems nice so far.
-
The KDL Document Language
While there's JSON5[1] now, it just has not the same level of native (ecosystem) support as JSON has.
[0]: https://github.com/ron-rs/ron
[1]: https://json5.org/
What are some alternatives?
toml.io - Source Code for toml.io
json5 - JSON5 — JSON for Humans
kdl - the kdl document language specifications
russian-words - List of Russian words
yaml-reference-parser
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
typescript-json-schema - Generate json-schema from your Typescript sources
yamllint - A linter for YAML files.
Amethyst - Data-oriented and data-driven game engine written in Rust
miniquad - Cross platform rendering in Rust
strictyaml - Type-safe YAML parser and validator.
cson - CoffeeScript-Object-Notation. Same as JSON but for CoffeeScript objects.