LIBUCL
hjson
Our great sponsors
| LIBUCL | hjson | |
|---|---|---|
| 5 | 5 | |
| 1,594 | 2,625 | |
| - | 0.7% | |
| 7.9 | 4.8 | |
| 3 days ago | 10 days ago | |
| C | HTML | |
| BSD 2-clause "Simplified" License | 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.
LIBUCL
-
That's a Lot of YAML
Have you seen ucl? https://github.com/vstakhov/libucl
It seems very similar.
-
Structured configuration in Go
Structured configuration is the type of configuration language I wanted for Djinn, whereby parameters could be grouped together into blocks, and nested within each other. Hence, the structure. The language I came up with was heavily influenced by HCL, and libucl and has support for duration and size literal values. Below is what the language looks like,
- Libucl: Universal configuration language parser library
- An Intuition for Lisp Syntax
-
The YAML file of Prometheus Operator has over 13k lines, one of the longest YAML files on GitHub ever
Here you go: https://github.com/vstakhov/libucl
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?
yaml-cpp - A YAML parser and emitter in C++
noyaml - A silly emotional rant about the state of devops tooling/the infrastructure sector in 2018. #noyaml.com
frozen - JSON parser and generator for C/C++ with scanf/printf like interface. Targeting embedded systems.
yj - CLI - Convert between YAML, TOML, JSON, and HCL. Preserves map order.
YAJL - A fast streaming JSON parsing library in C.
www.yaml.org - The yaml.org website
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API
cuetorials.com - Learn you some CUE for a great good!
JsonCpp - A C++ library for interacting with JSON.
json2jsii - Generates jsii-compatible structs from JSON schemas
Boost.PropertyTree - Boost.org property_tree module
json-c - https://github.com/json-c/json-c is the official code repository for json-c. See the wiki for release tarballs for download. API docs at http://json-c.github.io/json-c/