I&#x27;ve been trying to break this catch-22 by experimenting with a language&#x2F;VM&#x2F;codebase without any backwards-compatibility guarantees. Instead of freezing interfaces for others to use, I&#x27;m going to guarantee instead that I&#x27;ll have tests showing how to use my mechanisms, and you need to have tests for the programs you write using them. I&#x27;ll try to make breakage happen in obvious rather than subtle ways, but if you don&#x27;t write tests you&#x27;ll be in a world of hurt. If you write thorough tests, however, it might be a grand adventure as we hopefully keep the language supple over time. Who&#x27;s with me?<p>Probably nobody :) Oh well, I&#x27;ll be here by myself getting muddy in this foot path next to the highway. But it might be entertaining to read about what I&#x27;ve been up to.<p><a href="http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;libraries2" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;libraries2</a><p><a href="http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;readable-bad" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;readable-bad</a><p><a href="http:&#x2F;&#x2F;akkartik.name&#x2F;about" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;about</a><p><a href="http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;mu" rel="nofollow">http:&#x2F;&#x2F;akkartik.name&#x2F;post&#x2F;mu</a>