<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Archives on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/archives/</link>
    <description>Recent content in Archives on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/archives/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Archive Libraries in 2026: libarchive vs SharpCompress vs Commons Compress vs archiver</title>
      <link>https://www.pistack.xyz/posts/2026-09-27-archive-libraries-libarchive-sharpcompress-commons-compress-archiver-yauzl-comparison/</link>
      <pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-27-archive-libraries-libarchive-sharpcompress-commons-compress-archiver-yauzl-comparison/</guid>
      <description>&lt;p&gt;Every service eventually has to accept a file the user controls. The moment that file is a &lt;code&gt;.zip&lt;/code&gt; — a theme upload, a data import, a log bundle from a customer — you have two options: shell out to &lt;code&gt;tar&lt;/code&gt;/&lt;code&gt;unzip&lt;/code&gt; and inherit an argument-injection bug plus a process-per-request cost, or use a real archive library and handle the format&amp;rsquo;s edge cases deliberately.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
