Considering it translates to css, it obviously can be done in css.
The biggest argument is reuse and clarity. I'm not really a big fan, but the ability to generate rules in a polyvariant fashion from nested structures without having to explicitly detail each one can be a comparative benefit.
Many of the benefits of preprocessors have been merged into css itself in recent years, making them less essential.
AlgoRythm4763814d@SortOfTested @OP tl;dr to make up for CSS & browser shortcomings
I use SASS for breakpoints (think: bootstrap).
You can't use CSS3 variables in media queries and it will be a cold day in hell before I hard-code my values in CSS so I use SASS to to the ugly work for me.
Not to mention CSS3 variables still don't have 100% support, so you can't use them in a strict business environment where 100% browser coverage is a goal.
Since it needs to go through a compilation, there is also some basic error checking as well (though admittedly, it still won't catch almost any typical CSS typos like #botom-banner or .hidee)
Not to mention SASS isn't held down by politics like CSS is so it can get syntax features more quickly and doesn't have such a high pressure for backwards compatibility.
The last point in particular has a downside though: SASS may disappear one day, whereas CSS is very likely to be around forever.