<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Common-Lisp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/common-lisp/</link>
    <description>Recent content in Common-Lisp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/common-lisp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hunchentoot vs Caveman2 vs Clack in 2026: Which Common Lisp Web Stack Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-11-common-lisp-web-stack-hunchentoot-caveman-clack/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-11-common-lisp-web-stack-hunchentoot-caveman-clack/</guid>
      <description>&lt;p&gt;Common Lisp is the oldest language in this series and, by a strange coincidence, the one whose web stack is structured more sensibly than most modern alternatives. Ruby has Rack. Python has WSGI and ASGI. Node.js has a pile of competing abstractions. Common Lisp has had &lt;strong&gt;one&lt;/strong&gt; standard answer for over a decade, and the three projects people argue about are not really competitors at all — they are three layers of the same stack.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
