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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48277424 |
| Publication time | Tue, 26 May 2026 09:54:34 +0000 |
| Retrieval time | 2026-05-26T10:07:47.871Z |
| Last seen | 2026-05-26T10:07:47.871Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Lbz5VWMFV91J |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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.