<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Forth on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/forth/</link>
    <description>Recent content in Forth on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/forth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forth in 2026: Gforth vs pForth vs zeptoforth Compared</title>
      <link>https://www.pistack.xyz/posts/2026-09-14-forth-implementations-gforth-pforth-zeptoforth-guide/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-14-forth-implementations-gforth-pforth-zeptoforth-guide/</guid>
      <description>&lt;p&gt;Most languages in 2026 want to own your whole machine: a runtime, a package manager, a build system, and several hundred megabytes of dependencies. Forth does the opposite. A complete Forth development environment is a few thousand bytes of compiled code, an interactive REPL that can redefine any word while it is running, and a mental model so small that you can hold the entire language in your head.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
