libconfini
json5
libconfini | json5 | |
---|---|---|
8 | 94 | |
155 | 6,291 | |
- | 0.7% | |
0.0 | 0.0 | |
almost 2 years ago | 5 months ago | |
C | JavaScript | |
GNU General Public License v3.0 only | 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.
libconfini
-
Why the fuck are we templating YAML? (2019)
Personally I prefer INI over nearly all configuration formats.
https://github.com/madmurphy/libconfini/wiki/An-INI-critique...
- An INI Critique of TOML
- Do you call it an "ini" file or a "dot I N I" file?
- libconfini: Yet another INI parser
- An INI critique of TOML
-
YAML: The Missing Battery in Python
Essentially the reasons given here. (This is from an INI parser developer, but I don’t think it’s particularly biased.)
- If a linux/unix was rewritten today, what would be different?
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?
config-parser - A slim, fully managed C# library for reading/writing .ini, .conf, .cfg etc configuration files.
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
hjson-js - Hjson for JavaScript
ini-parser - Read/Write an INI file the easy way!
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
toml - Tom's Obvious, Minimal Language
crudini - A utility for manipulating ini files
jsonnet - Jsonnet - The data templating language
guile-gi - Bindings for GObject Introspection and libgirepository for Guile
sublime-hjson - Hjson support for Sublime Text