Original Summary

I started hacking with TRS-80 Basic long ago. By the time I went pro in my early 20&#x27;s, I had already developed a strong preference for declarative systems, so much so that I would from time to time create one if it made the solution at hand more robust. Having studied Physics instead of CompSci, I came to this preference outside of any knowledge of the existing arguments for&#x2F;against or the vocabulary used in the literature. For me it was a simple process: discern common patterns in the imperative code, establish a data structure that captured them, write something to process them.<p>The commercial motivation was always the correctness guarantee, but the yak-shaving exercise of building the system offered the satisfaction that purely commercial concerns could not provide.<p>Now, in the dawn of the age of LLM coding, I find the agents are &quot;unreasonably effective&quot; at coding to declarative systems. The entire reference for the data format or DSL can fit in context, and LLMs are naturally more reliable against a constrained system. Compare to CSS, highly unconstrained, where I find code duplication, then conflict, then the inevitable !important flags begin to proliferate.<p>Yet, as anybody who enjoys the benefits of declarative systems will tell you, it can be lonely. The world prefers a general purpose imperative system. I believe the biggest reason is that the open-ended imperative system does not force us into a mapping exercise before we get to work. The code is like a whiteboard, where ideas are tried and modified in flight.<p>But I&#x27;d like to hear from others. Which do you prefer and why? In what situations?

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/9/23 20:58:11