Our great sponsors
| json5 | ron | |
|---|---|---|
| 94 | 24 | |
| 6,278 | 3,118 | |
| 1.1% | 2.5% | |
| 0.0 | 7.9 | |
| 5 months ago | 12 days ago | |
| JavaScript | 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.
json5
- JSON5 – JSON for Humans
- Why the fuck are we templating YAML? (2019)
-
I pre-released my project "json-responder" written in Rust
JSON5 support
-
topoconfig: enhancing config declarations with graphs
Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.
-
That's a Lot of YAML
I think JSON5 is fairly close to this: https://json5.org
I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:
key: this is my value
(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)
-
XML is better than YAML
I believe that's JSON5.
https://github.com/json5/json5
It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.
- Fx – Terminal JSON Viewer
- What Is Wrong with TOML?
-
🚀 'GET' API in API Maker
JSON 5 support
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
I would like to see mention of JSON5 which is 11 years its elder. For comments in JSON, JSON5 is a good starting point.
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?
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
toml.io - Source Code for toml.io
hjson-js - Hjson for JavaScript
kdl - the kdl document language specifications
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
toml - Tom's Obvious, Minimal Language
yaml-reference-parser
jsonnet - Jsonnet - The data templating language
typescript-json-schema - Generate json-schema from your Typescript sources
sublime-hjson - Hjson support for Sublime Text
yamllint - A linter for YAML files.