4 ms·
From the website: > New tools like CUE, jsonnette, PKL, and others have emerged to address some of the short comings of raw YAML configuration and templating.
by sepositus 2y ago
From the website:
> New tools like CUE, jsonnette, PKL, and others have emerged to address some of the short comings of raw YAML configuration and templating. Inspiring new K8s package managers such as timoni. However it is yoke’s stance that these tools will always fall short of the safety, flexibility and power of building your packages from code.
The never-ending debate continues between configuration languages and traditional languages. I don't know if the industry will ever standardize in this area.
- Kinrany 2y agoIt will once traditional languages are good enough
- bbkane 2y agoI disagree - I think there are fundamental tradeoffs between declarative and imperative ways of configuration so they'll never "converge" completely. I am a huge fan of each camp stealing ideas from the other and thus "converging" closer. I also like the two-step "write imperative code to generate declarative config" approach some systems take - Terraform/Pilumi do this. At the cost of having two steps, you get to write your for loops AND get a declarative "state" you can diff easily with the previous state.
- Kinrany 2y agoConfiguration languages are just structured data, and programming languages also need to be able to express complex literal data. JSON is already explicitly designed as a ~subset of JavaScript. An equivalent of a JSON written as a JavaScript literal is easier to read than JSON. The only problem is that we often don't want to use an interpreter to parse data.
- fire_lake 2y agoTraditional languages will not remove the features that make them poor for configuration. I can’t imagine Python dropping the ability to query the current date, for example.