<p>I've seen a lot of recent posts that ask questions like "Is it time to stop writing Sass?".</p>
<p>I haven't written a Less or Sass stylesheet since I adopted utility classes and Tachyons, and then Tailwind CSS, and I moved to PostCSS.</p>
<p>But, with recent native browser support added for some Sass features, such as <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_nesting">CSS nesting</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties">CSS custom properties</a> (variables), people are considering moving from Sass to regular CSS.</p>
<p>Using regular CSS also makes it easier to onboard new Developers onto your project, which is particularly helpful in open-source projects, as <a href="/podcast/11-mark-conroy">Mark Conroy and I discussed</a> on the Beyond Blocks podcast.</p>
format:full_html
processed:|
<p>I've seen a lot of recent posts that ask questions like "Is it time to stop writing Sass?".</p>
<p>I haven't written a Less or Sass stylesheet since I adopted utility classes and Tachyons, and then Tailwind CSS, and I moved to PostCSS.</p>
<p>But, with recent native browser support added for some Sass features, such as <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_nesting">CSS nesting</a> and <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties">CSS custom properties</a> (variables), people are considering moving from Sass to regular CSS.</p>
<p>Using regular CSS also makes it easier to onboard new Developers onto your project, which is particularly helpful in open-source projects, as <a href="/podcast/11-mark-conroy">Mark Conroy and I discussed</a> on the Beyond Blocks podcast.</p>