3 ms·
It’s a lot more complicated than YAML though. What’re the advantages? Who’s actually using it?
by vosper 4y ago
It’s a lot more complicated than YAML though. What’re the advantages? Who’s actually using it?
- mirekrusin 4y agoTerseness - you can describe exactly what you want without repetition at arbitrary cross-sections Intuitive behavior - unification by design is unordered (ie. it doesn't matter in which order input is processed, it'll produce the same result), you get what you see. Verification - ie. you can do one-liner policies easily to have some structure with desired types/values etc. It's just well designed (based on good theory), practical language for configuration. We use it in critical project to describe services on different envs, it works very well.
- mdaniel 4y agoThe new docker-based CICD system uses cue: https://docs.dagger.io/1235/what#how-does-it-work https://docs.dagger.io/1235/what#how-does-it-work
- moderation 4y agoThere are few things more complicated that YAML - https://www.arp242.net/yaml-config.html#its-pretty-complex https://www.arp242.net/yaml-config.html#its-pretty-complex > YAML may seem ‘simple’ and ‘obvious’ when glancing at a basic example, but turns out it’s not. The YAML spec is 23,449 words; for comparison, TOML is 3,339 words, JSON is 1,969 words, and XML is 20,603 words. Grafana Labs, Datadog's Vector, the Istio Service Mesh project, Dagger, sigstore, the SLSA framework all use CUE in some fashion. Dagger wrote a great blog post on CUE [0] 0. https://docs.dagger.io/1215/what-is-cue/ https://docs.dagger.io/1215/what-is-cue/