Occasionally, you might see an opportunity to make your own mixins to simplify your site and make your design easier to maintain. When you do, you'll be glad that the mechanisms for abstraction are there for you too, not hidden away from the "designers who have to be protected from code".
At least with CSS, everyone is speaking the same language. Also, most big websites end up having CSS in other places other than a central location driven by sass. You'll probably end up having some element level css, maybe a few scattered in various jquery plugins, or one-line jquery hacks for modifying css classes or changing colors etc.
Wrong. There are many designers who love sass and they kick some serious ass. Actually, EVERY designer with whom I've sat down with and shown them sass and compass has fallen in love with it.
> At least with CSS, everyone is speaking the same language.
By this logic every programmer should still be programming in COBOL and FORTRAN. But the reality is that every decade or so, a new language comes along and moves the industry in a new direction. Well guess how old CSS is? CSS is getting serious scrutiny now because there are so many programmers doing front end implementation now. I've used CSS. In fact, I'm great at CSS, but we can do better and be more efficient.
Variables, arithmetical, and mixin abstractions make the team integration much smoother. All this, and the learning curve is incredibly small.
In this case SASS doesn't need that. Every major and most minor languages can do variables and loops. Wouldn't it be more intelligent to focus on getting SASS as a universal way for programming languages to work with styling instead of making SASS a programming language?
At some point you have to stop and think about what's better for the community.
A niche programming language that brings very little to the table much less anything done well is not good for the community.