cue

So is CUE. See the section on types and values here - https://github.com/cuelang/cue/blob/master/doc/tutorial/basi...

It’s interesting for me to see a project made mostly by 1 person that happens to be employed by Google described as “by Google”. [1] Not that there’s no truth to it, just that the reality is much more nuanced than a simple phrase can capture. [1] https://github.com/cuelang/cue/graphs/contributors

This issue is a good comparison of the two approaches: https://github.com/cuelang/cue/issues/33

The JSON sugar way too much for me. See folding as an example https://github.com/cuelang/cue/blob/master/doc/tutorial/basi...

I think it is mostly about being able to declare the config schema in the same language. You can declare a base config file with types instead of values that has to be extended. The parser will validate the types and insert defaults when it is merging the configs. It also has some nice features to avoid duplication and boilerplate. References: https://github.com/cuelang/cue/blob/master/doc/tutorial/basi... Disjunctions: https://github.com/cuelang/cue/blob/master/doc/tutorial/basi... Templates: https://github.com/cuelang/cue/blob/master/doc/tutorial/basi...

Couple of contenders: - Jsonnet (https://jsonnet.org/) - simpler syntax and less concepts to learn, just an extension of JSON. But no type checking. An open source offspring of Google's internal config language (GCL/BCL) - Cue (https://github.com/cuelang/cue) - a more ambitious attempt to fix GCL/BCL by replacing inheritance as the fundamental compositional primitive with constraint unification. Great thread comparing them against each other by the authors of both: https://github.com/cuelang/cue/issues/33 Cue seems kind of similar to Dhall on first sight, but I haven't used either enough for an informed opinion yet.