提问 HN：在后 LLM 时代，YAML 还有用武之地吗？
1 分•作者: throwaw12•大约 1 个月前
想听听您对 YAML 以及其他旨在将工作流/流程从软件工程（命令式）转向配置（声明式）的 DSL 的看法。
以 K8s 为例，它有大量的 YAML 配置，这些配置原本是为了方便人类阅读。但在有了 LLM 之后，我们是否还需要它们？
有了 LLM，是不是直接说：“用 10 个 Pod 暴露这项服务，并且只启用内部路由”会更容易？然后 LLM 就可以更新几行 Python 代码（比如 Pulumi、AWS CDK 等），而不是生成 5 个 YAML 文件，每个文件至少有 40 行 YAML，并且还要尝试复用相同的属性/标签/标记。
查看原文
Curious to know your opinion about YAML and other DSL created to make workflows/processes less software engineering (imperative) and more configuration (declarative).<p>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?<p>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