<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sass on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sass/</link>
    <description>Recent content in Sass on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sass/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostCSS vs Sass vs Lightning CSS in 2026: Rebuilding Your CSS Pipeline</title>
      <link>https://www.pistack.xyz/posts/2026-08-11-postcss-sass-lightningcss-css-build-pipeline-comparison/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-11-postcss-sass-lightningcss-css-build-pipeline-comparison/</guid>
      <description>&lt;p&gt;Your CSS build step is probably the most ignored performance lever in your frontend. Every page load pays for it, yet most teams still run a toolchain chosen in 2018 because &amp;ldquo;it works.&amp;rdquo; In 2026 the calculus has changed: native CSS now ships nesting, custom properties, and &lt;code&gt;color-mix()&lt;/code&gt;, browsers update on a six-week cadence, and a new Rust-powered compiler is 50-100x faster than the JavaScript tools we&amp;rsquo;ve all been running. The three serious contenders are &lt;strong&gt;PostCSS&lt;/strong&gt; (28,982 stars — the plugin platform), &lt;strong&gt;Sass&lt;/strong&gt; (15,376 stars — the veteran preprocessor), and &lt;strong&gt;Lightning CSS&lt;/strong&gt; (7,649 stars — the Rust speed demon from the Parcel team). Here&amp;rsquo;s how to choose, with real configs and honest trade-offs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
