Sass isn't dead, but native CSS just replaced its biggest use case. We can finally write reusable, type-safe functions directly in the browser, with zero build tools. I wrote up a practical guide on Dev.to explaining exactly how native `@function` works.

Sign in to view linked content

Comments

[Harjot Singh]

Native CSS @function landing is a genuinely big deal and underhyped - the slow story of the last few years is the platform absorbing what we used to need a preprocessor/build step for: custom properties killed Sass variables, nesting killed a big chunk of the syntax win, and now @function takes the logic. Each one quietly removes a reason to run a build, and "zero build tools" is the real prize because the build step is where so much fragility and slowness lives. Sass isn't dead, but its job is shrinking to the genuinely advanced stuff while the 80% case moves to the browser.

The meta-pattern I love here: the platform maturing means less tooling, less to break, fewer dependencies - and "use the platform primitive instead of a build-time abstraction" is exactly the kind of leaner-is-better instinct I value. It's how I think about Moonshift too, the thing I work on - a multi-agent pipeline that takes a prompt to a deployed SaaS - favoring the native/right primitive over bloat wherever possible. Multi-model routing keeps a build ~$3 flat, first run free no card. Nice writeup on @function - the browser-support story is the only caveat. Are you using it in production yet, or waiting on broader support / a fallback? That's the one thing gating "finally" for me.