<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scopt on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/scopt/</link>
    <description>Recent content in Scopt on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/scopt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>scopt vs decline vs Scallop in 2026: Which Scala CLI Parser Should You Ship?</title>
      <link>https://www.pistack.xyz/posts/2026-11-15-scala-cli-parsers-scopt-decline-scallop/</link>
      <pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-15-scala-cli-parsers-scopt-decline-scallop/</guid>
      <description>&lt;p&gt;Every Scala service eventually grows a command-line entry point, and the first ten minutes of that work decide how the next two years feel. Parse arguments with &lt;code&gt;args(0)&lt;/code&gt; and you will be rewriting the whole thing when someone asks for &lt;code&gt;--dry-run&lt;/code&gt;; pick a library casually and you inherit its error messages, its help output, and its opinions about subcommands forever. There are exactly three contenders that matter in 2026, and they are philosophically incompatible.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
