<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Stencil on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/stencil/</link>
    <description>Recent content in Stencil on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/stencil/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Components in 2026: Lit vs FAST vs Stencil — Which Should You Actually Build On?</title>
      <link>https://www.pistack.xyz/posts/2026-10-17-web-components-lit-fast-stencil-comparison/</link>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-17-web-components-lit-fast-stencil-comparison/</guid>
      <description>&lt;p&gt;Every frontend team has a rewrite scar. The framework that felt inevitable five years ago is now a maintenance item, and the component library built on top of it is welded to a version that is no longer supported. Web Components are the one part of the browser platform that outlives the framework cycle: &lt;code&gt;&amp;lt;status-badge&amp;gt;&lt;/code&gt; is a custom element today, in five years, and after the next three framework migrations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
