libconfini
hjson
libconfini | hjson | |
---|---|---|
8 | 5 | |
155 | 2,625 | |
- | 0.3% | |
0.0 | 4.8 | |
almost 2 years ago | 13 days ago | |
C | HTML | |
GNU General Public License v3.0 only | MIT License |
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?
hjson
-
Why the fuck are we templating YAML? (2019)
HJson https://hjson.github.io seems a nice 'in-between' between YAML and JSON without the indentation-based syntax, so closer to the JSON side but with comments and less quotes.
What I don't really get is why the cloud providers / tooling implementors have never drafted up a "YAML-light" that just throws out the rarely-used headache-inducing syntax elements.
-
That's a Lot of YAML
Hjson is very similar to JSON5 but allows quotes to be dropped and can use newlines instead of commas. There are implementations for a lot of different languages, I myself contributed the C++ implementation. I wanted something smaller than Yaml but more lax than JSON, found Hjson to suit my needs perfectly.
https://hjson.github.io/
-
The real reason JSON has no comments
JSONs make terrible config files. If you want to use json-like syntax for config, use hjson instead. It's basically json, but changes it slightly so it better matches human expectations.
-
The YAML Document from Hell
```
YAML and JSON succeeded because they had a clean and predictable, no-nonsense mapping between encoding and object-model after decoding. Probably we should all switch to an almost-yaml format that does away with the peculiarities, and the FANG companies would have the momentum to make that happen.
I personally would like for HJSON (https://hjson.github.io) to see more adoption, but that train has passed...
-
Why?
There’s also json-c and Hjson.
What are some alternatives?
config-parser - A slim, fully managed C# library for reading/writing .ini, .conf, .cfg etc configuration files.
noyaml - A silly emotional rant about the state of devops tooling/the infrastructure sector in 2018. #noyaml.com
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
yj - CLI - Convert between YAML, TOML, JSON, and HCL. Preserves map order.
ini-parser - Read/Write an INI file the easy way!
LIBUCL - Universal configuration library parser
toml - Tom's Obvious, Minimal Language
www.yaml.org - The yaml.org website
crudini - A utility for manipulating ini files
cuetorials.com - Learn you some CUE for a great good!
guile-gi - Bindings for GObject Introspection and libgirepository for Guile
json2jsii - Generates jsii-compatible structs from JSON schemas