<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hotwire on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hotwire/</link>
    <description>Recent content in Hotwire on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hotwire/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Phoenix LiveView vs Laravel Livewire vs Hotwire Turbo in 2026: Which Server-Rendered UI Stack Wins?</title>
      <link>https://www.pistack.xyz/posts/2026-11-02-phoenix-liveview-vs-livewire-vs-hotwire-turbo/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-02-phoenix-liveview-vs-livewire-vs-hotwire-turbo/</guid>
      <description>&lt;p&gt;Single-page apps promised snappy interfaces and delivered a second backend: a JSON API, a state store, a router, and a build pipeline to keep them in sync. By 2026 a lot of teams have quietly walked that back — not to jQuery-style spaghetti, but to a third model where the server renders HTML and pushes updates over a socket, and the browser holds almost no application state.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
