SCSS Is Solving Problems CSS Is Learning to Solve Itself

You've spent years reaching for SCSS the moment a project grows past a single stylesheet. Variables. Loops. Functions. Nesting. It felt like the only sane way to write scalable CSS. Meanwhile, native CSS has been quietly shipping the same features — one by one, browser by browser. So here's the honest question: how much of SCSS do you actually still need? Let me walk through what CSS can do natively today, what's coming next, and where SCSS still wins. What CSS Can Do Right Now Custom Properties (aka CSS Variables) You already know these. They replaced SCSS $variables for runtime use-cases — and they're strictly more powerful because they cascade, they're dynamic, and JavaScript can interact with them. :root { --color-primary: #ff69b4; --spacing-base: 8px; } .button { background: var(--color-primary); padding: calc(var(--spacing-base) * 2); } SCSS variables are build-time only. Custom properties survive into the browser. If you haven't fully made the switch for your design tokens, that