CONL: "Markdown" for your config files

1. nestedtext

   1 10 382 7.8 Python

   Human readable and writable data interchange format

   

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. json5

   2 104 6,902 2.5 JavaScript

   JSON5 — JSON for Humans

   

   https://json5.org/

   > The first version of CONL used # as a comment token, but I quickly ran into issues. URLs contain #, so my next version...

   Every other language has figured this one out as well. Wrap strings in quotation marks.

   > That led to a data-model where each value is one of scalar|list|map (Compared to JSON’s null|bool|number|string|object|array, this felt good).

   I'm not sure what a "scalar" is in CONL (is it always a string?) but having fewer types than JSON is not a positive feature for a config file format. Even JSON's hand-wavy "number" type is problematic and TOML got it right to distinguish integers from floats.

4. hcl

   3 50 5,521 7.8 Go

   HCL is the HashiCorp configuration language.

   

   Similar to HCL which is way safer and clearer IMHO than all indent based craziness. Its lovely to see default values loaded thanks to some extra spaces. Brackets for the win!

   https://github.com/hashicorp/hcl

Suggest a related project