Search posts, tags, users, and pages
If you like.... .....a lot more features use Stylus .....building your own bespoke language use postCSS .....javascript-purity use Less
Each have their own strengths, but there is a reason why Sass has only gained in usage over time. In fact, while we're the first CSS processor, we were for quiet a while not the most popular. But, over time, we've just kind of stuck to our slow, methodical improvement cycles and positioning... ending up being a kind of de-facto standard. And, that's due to Natalie and Chris' amazing stewardship of the language, plus the awesome LibSass/Node-Sass team (Michael and company), plus the awesome community organizers we have.
But, hell, there's no ego in web development. If one of those solutions works better, then party on Wayne.
I use several postcss plugins along side Sass in development: autoprefixer, rtlcss, postcss lang optimizer. The ability to work directly with the AST in postcss is very powerful for a certain class of CSS processing -- especially those cases where you rarely, if ever, want to opt-out of the change.
For traditional preprocessors I couldn't imagine using anything other than Sass.
Things like Styled Components are really great too.