<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Styling on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/styling/</link>
    <description>Recent content in Styling on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 15 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/styling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSS-in-JS in 2026: styled-components vs Emotion vs Linaria — Which One Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-15-css-in-js-styled-components-emotion-linaria-comparison/</link>
      <pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-15-css-in-js-styled-components-emotion-linaria-comparison/</guid>
      <description>&lt;p&gt;A single CSS-in-JS mistake costs real money: when Stripe migrated away from runtime CSS-in-JS in 2022, they reported a &lt;strong&gt;~7% end-to-end render speedup&lt;/strong&gt; by eliminating the runtime overhead, and when Shopify analyzed their own stack they found React re-renders were triggering style recalculation across entire style sheets — not just the component that changed. Yet at the same time, the developer experience of scoped, typed, dead-code-eliminated styling is so good that CSS-in-JS libraries still power the majority of production React apps. The tension is simple: runtime CSS-in-JS gives you the best DX but taxes your users&amp;rsquo; CPUs; zero-runtime approaches give performance back but cost you features. In 2026, the three libraries that define this spectrum are styled-components (41,125 stars), Emotion (18,017 stars), and Linaria (12,347 stars) — and the right choice depends almost entirely on one question: &lt;strong&gt;can your team afford the runtime?&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
