<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zstandard on Nalar</title>
    <link>https://nalar.dev/tags/zstandard/</link>
    <description>Recent content in Zstandard on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/zstandard/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Zstandard Compression with Python compression.zstd</title>
      <link>https://nalar.dev/use-zstandard-compression-with-python-compression-zstd/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/use-zstandard-compression-with-python-compression-zstd/</guid>
      <description>&lt;p&gt;Python applications have long had standard-library support for gzip, bzip2, LZMA, and zlib. Python 3.14 adds another important option: Zstandard support through &lt;code&gt;compression.zstd&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Zstandard is useful when a system needs a practical balance of compression ratio and throughput. The new module means many applications can read and write &lt;code&gt;.zst&lt;/code&gt; data without adding a third-party Python package. But choosing a compression API is not only about calling &lt;code&gt;compress()&lt;/code&gt; and &lt;code&gt;decompress()&lt;/code&gt;. Production code also needs to think about streaming, memory limits, frame boundaries, dictionaries, compatibility, and untrusted input.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
