<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>theChris.in — Systems, Failure, Longevity</title><link>https://thechris.in/tags/language-design/</link><description>Essays on systems, failure modes, and building software that lasts.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@thechris.in (Chris Roy)</managingEditor><webMaster>hello@thechris.in (Chris Roy)</webMaster><copyright>© 2025 theChris.in. Read freely. Attribute generously. #obviously</copyright><lastBuildDate>Tue, 21 Jul 2026 03:55:57 +0530</lastBuildDate><atom:link href="https://thechris.in/tags/language-design/index.xml" rel="self" type="application/rss+xml"/><item><title>On programming language design and the problem of forgotten decisions</title><link>https://thechris.in/articles/on-programming-language-design-and-the-problem-of-forgotten-decisions/</link><pubDate>Tue, 21 Jul 2026 03:55:57 +0530</pubDate><author>hello@thechris.in (Chris Roy)</author><guid isPermaLink="true">https://thechris.in/articles/on-programming-language-design-and-the-problem-of-forgotten-decisions/</guid><description>Most programming languages are remembered for their syntax.&amp;#xA;Almost none are remembered for the decisions that produced it.&amp;#xA;Every keyword exists because someone decided one approach was better than another. The debate took weeks. The implementation took hours. The reasoning lasted …</description><category>Architecture</category><category>Language-Design</category></item></channel></rss>