| kdl-rs | json5 | |
|---|---|---|
| 2 | 94 | |
| 282 | 6,301 | |
| 2.1% | 0.9% | |
| 1.2 | 0.0 | |
| 30 days ago | 5 months ago | |
| Rust | JavaScript | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
kdl-rs
-
The KDL Document Language
To me it looks amazing, and I was literally about to adopt it in one of my open source Rust-based projects, but then I realized that the Rust version (and only the Rust version) is restrictively licensed under the Parity Public License [1].
I want my open source project to be able to be used in commercial applications, and don't want any of my dependencies' licenses to restrict that.
[1]: https://github.com/kdl-org/kdl-rs/blob/87f836134c1d901ff5ce6...
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.
What are some alternatives?
Slim - Slim is a template language whose goal is to reduce the syntax to the essential parts without becoming cryptic.
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
kdl4j - KDL Parser for the JVM
hjson-js - Hjson for JavaScript
Kaitai Struct - Kaitai Struct: declarative language to generate binary data parsers in C++ / C# / Go / Java / JavaScript / Lua / Nim / Perl / PHP / Python / Ruby
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
ron - Rusty Object Notation
toml - Tom's Obvious, Minimal Language
kaydle - An alternative implementation of Kat's Document Language, including serde integration
jsonnet - Jsonnet - The data templating language
kdl - the kdl document language specifications
sublime-hjson - Hjson support for Sublime Text