Is it Time to Un-Sass? | CSS-Tricks
September 23, 2025
By my count, I have been using Sass for over 13 years. I chose Sass over Less.js because I thought it was a better direction to go at the time. And my bet paid off. That is one of the difficult things about working in the technical space. There are a lot of good tools but some end up rising to the top and others fall away. I have been pretty fortunate that most of the decisions I have made have gone the way that they have. All the agencies I have worked for have used Sass.
The last 15 years or so of web development has been about adding layers of abstraction to help tame the complexity of the underlying languages and APIs. When I say that you’re probably thinking about something like React or Angular, but this has also happened with the world of CSS.
SASS probably took hold even earlier than libraries and frameworks like React, and it has been a staple in many professional developer’s stack for a decade or more now.
SAS was always about helping manage complexity of CSS and introduced many concepts that have now been absorbed into standard CSS (to name just a couple).
Just as the implementation of features from jQuery like QuerySelector and Fetch meant we increasingly didn’t need jQuery, it is the same happening with Sass as well?
