<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scripting on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/scripting/</link>
    <description>Recent content in Scripting on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/scripting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Bash Scripting Frameworks: bashly vs bashew vs argbash — Build Production-Grade CLI Tools in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-17-self-hosted-bash-scripting-frameworks-bashly-bashew-argbash/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-17-self-hosted-bash-scripting-frameworks-bashly-bashew-argbash/</guid>
      <description>&lt;h2 id=&#34;why-use-a-bash-scripting-framework&#34;&gt;Why Use a Bash Scripting Framework?&lt;/h2&gt;&#xA;&lt;p&gt;Bash is everywhere &amp;ndash; it ships on every Linux distribution, every macOS machine, and every WSL instance. But writing maintainable, production-grade Bash scripts is surprisingly hard. Without structure, shell scripts quickly devolve into unreadable spaghetti with zero test coverage and no consistent argument handling.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
