<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rhai on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/rhai/</link>
    <description>Recent content in Rhai on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/rhai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Embedded Scripting in Rust in 2026: Rhai vs Rune vs mlua Compared</title>
      <link>https://www.pistack.xyz/posts/2026-11-05-rust-embedded-scripting-rhai-rune-mlua/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-05-rust-embedded-scripting-rhai-rune-mlua/</guid>
      <description>&lt;p&gt;Every nontrivial Rust service eventually grows the same feature request: let someone else supply the logic. Pricing rules, alert thresholds, webhook transforms, workflow steps, game behaviors — the moment a customer asks to change one without a redeploy, you are choosing an embedded scripting engine. Recompiling a plugin as a &lt;code&gt;cdylib&lt;/code&gt; gives you no sandbox, no resource accounting, and ABI breakage on every toolchain bump; embedding an interpreter gives you all three.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
