Ask HN: Is there a need for YAML in post-LLM world?
The article discusses the relevance of YAML in the context of large language models (LLMs). It questions whether the declarative nature of YAML is still necessary when LLMs can simplify configurations through natural language commands. The author uses Kubernetes as an example to illustrate the potential shift in workflow management.
- ▪The article poses a question about the need for YAML in a post-LLM world.
- ▪It suggests that LLMs could streamline the process of service configuration.
- ▪Kubernetes is cited as an example where YAML is heavily used for human readability.
Opening excerpt (first ~120 words) tap to expand
Curious to know your opinion about YAML and other DSL created to make workflows/processes less software engineering (imperative) and more configuration (declarative).Take a look at K8s for example, lots and lots of YAML configurations, which was used for human readability, but with LLMs do we still need them?Wouldn't it be easier with LLMs to say: expose this service with 10 pods and enable only internal routing - which then updates couple lines of Python code (pulumi, aws cdk and etc,.) instead of generating 5 yaml files each with at least 40 lines of YAML and also try to reuse same attributes/labels/tags
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.