<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tcl on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/tcl/</link>
    <description>Recent content in Tcl on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/tcl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tcl Web Stacks in 2026: NaviServer vs Apache Rivet vs OpenACS Compared</title>
      <link>https://www.pistack.xyz/posts/2026-09-16-tcl-web-stacks-naviserver-apache-rivet-openacs-comparison/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-16-tcl-web-stacks-naviserver-apache-rivet-openacs-comparison/</guid>
      <description>&lt;p&gt;Most developers write off Tcl as a language that died with the dot-com boom. Then you check the commit log: &lt;strong&gt;NaviServer&amp;rsquo;s repository received a commit on September 15, 2026&lt;/strong&gt;, Apache Tcl Rivet was pushed on &lt;strong&gt;August 30, 2026&lt;/strong&gt;, and OpenACS core on &lt;strong&gt;August 31, 2026&lt;/strong&gt;. These are not museum pieces on life support — they are small, focused, actively maintained codebases that still serve real deployments, and they solve a problem most modern stacks handle badly: &lt;strong&gt;running long-lived, single-process business logic with almost no memory overhead.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
