<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pony on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pony/</link>
    <description>Recent content in Pony on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 30 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pony/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pony Toolchain in 2026: ponyc vs Corral vs Stallion — Is Capability-Secure Actor Programming Worth It?</title>
      <link>https://www.pistack.xyz/posts/2026-10-30-pony-toolchain-ponyc-corral-stallion/</link>
      <pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-30-pony-toolchain-ponyc-corral-stallion/</guid>
      <description>&lt;p&gt;Your actor system passed 4,000 unit tests, survived a staging soak, and still deadlocked eight minutes into Black Friday. That is the dirty secret of message-passing concurrency: the compiler never told you that two actors could touch the same mutable state, because in most languages it &lt;em&gt;cannot&lt;/em&gt; tell you. Pony was built to close that hole — every reference in Pony carries a &lt;strong&gt;reference capability&lt;/strong&gt; (&lt;code&gt;iso&lt;/code&gt;, &lt;code&gt;val&lt;/code&gt;, &lt;code&gt;ref&lt;/code&gt;, &lt;code&gt;box&lt;/code&gt;, &lt;code&gt;trn&lt;/code&gt;, &lt;code&gt;tag&lt;/code&gt;) and the compiler rejects any program where a data race is structurally possible. No locks, no &lt;code&gt;synchronized&lt;/code&gt;, no runtime race detector needed: races become type errors.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
