cson
ron
Our great sponsors
| cson | ron | |
|---|---|---|
| 1 | 24 | |
| 1,334 | 3,118 | |
| 0.1% | 2.5% | |
| 5.7 | 7.9 | |
| 4 months ago | 15 days ago | |
| CoffeeScript | Rust | |
| GNU General Public License v3.0 or later | 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.
cson
-
The Norway Problem
I prefer JSON over YAML because I spend more time confused and burned by the problems caused by it.
I understand that people don't like directly use JSON because it's not very friendly: no comments, no multi-line string, etc.
A great alternative IMHO is cson[0]. It's like JSON to JavaScript but for CoffeeScript (though nobody talks about it nowadays). It has indentation-based syntax, comments, and multiline string which usually don't need to escape. The advantage is it's close enough to JSON which is the canonical format that everybody can agree on nowadays. For YAML and TOML there are too many visual part-aways from JSON.
Or just create a JSON variant that enables comments and the backtick multiline string from JavaScript.
[0] https://github.com/bevry/cson
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?
jsonnet - Jsonnet - The data templating language
toml.io - Source Code for toml.io
strictyaml - Type-safe YAML parser and validator.
json5 - JSON5 — JSON for Humans
edn - Extensible Data Notation
kdl - the kdl document language specifications
cue - CUE has moved to https://github.com/cue-lang/cue
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
bip39 - BIP-39 tools using Node and implemented in Coffeescript
yaml-reference-parser
lua-patterns - Exposing Lua string patterns to Rust
typescript-json-schema - Generate json-schema from your Typescript sources