<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Formats on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/data-formats/</link>
    <description>Recent content in Data-Formats on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/data-formats/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kaitai Struct vs binrw vs ImHex in 2026: Which Binary Format Toolkit Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-25-binary-format-parsing-kaitai-struct-binrw-imhex-hachoir/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-25-binary-format-parsing-kaitai-struct-binrw-imhex-hachoir/</guid>
      <description>&lt;p&gt;Every undocumented file format you have ever had to read has cost you the same afternoon: a hex dump on one screen, a format specification PDF on the other, and a growing pile of &lt;code&gt;offset += 4&lt;/code&gt; arithmetic that silently breaks the moment a new firmware revision ships. I have watched teams spend a full sprint on a vendor&amp;rsquo;s proprietary telemetry log, then re-do the whole job in Rust six months later because nobody wrote the layout down.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
