<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Phoenix on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/phoenix/</link>
    <description>Recent content in Phoenix on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/phoenix/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Elixir Web Development in 2026: Phoenix vs Plug vs Ash — Which Stack Should You Build On?</title>
      <link>https://www.pistack.xyz/posts/2026-08-12-elixir-web-frameworks-phoenix-plug-ash-comparison/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-12-elixir-web-frameworks-phoenix-plug-ash-comparison/</guid>
      <description>&lt;p&gt;Elixir keeps winning the &amp;ldquo;language I want to use but my team won&amp;rsquo;t let me&amp;rdquo; polls, and the reason is usually the same: the ecosystem around Phoenix has become genuinely excellent — but the choice of &lt;em&gt;how&lt;/em&gt; to build your web application is now three-way. Do you reach for the full batteries-included Phoenix framework with LiveView and Ecto? Do you compose bare functions with Plug and pick every piece yourself? Or do you adopt Ash, the declarative framework that generates your API, your authorization rules, and your persistence layer from resource definitions? In 2026 this is not a religious debate — it is a scoping decision with real consequences for team velocity, maintenance cost, and how long your abstractions survive. This guide compares all three with real code from the official repositories so you can decide on facts, not folklore.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
