<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wasi on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/wasi/</link>
    <description>Recent content in Wasi on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/wasi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>wasm-tools vs wit-bindgen vs WAC in 2026: Building WASI Components That Actually Ship</title>
      <link>https://www.pistack.xyz/posts/2026-10-24-wasm-tools-wit-bindgen-wac-component-model-guide/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-24-wasm-tools-wit-bindgen-wac-component-model-guide/</guid>
      <description>&lt;p&gt;WebAssembly&amp;rsquo;s component model stopped being a research demo somewhere in 2025. The problem is that the documentation never caught up: a newcomer runs &lt;code&gt;cargo build --target wasm32-unknown-unknown&lt;/code&gt;, ships a &lt;code&gt;.wasm&lt;/code&gt; file, and discovers that nobody can call it — because it exports a memory blob, not a typed interface. The gap between &amp;ldquo;a Wasm module exists&amp;rdquo; and &amp;ldquo;a component with a versioned interface that a host can link&amp;rdquo; is exactly where three command-line tools live: &lt;strong&gt;&lt;code&gt;wasm-tools&lt;/code&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;code&gt;wit-bindgen&lt;/code&gt;&lt;/strong&gt;, and &lt;strong&gt;&lt;code&gt;wac&lt;/code&gt;&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
