I too come from a background of "before CSS" and hand-coding HTML. But I differ completely as to why we should use SASS/Less. So addressing her misgivings in o

I too come from a background of "before CSS" and hand-coding HTML. But I differ completely as to why we should use SASS/Less. So addressing her misgivings in order: 1. Code bloat happens—whether hand-crafted or automatic bloat. A good designer will always fight bloat, and a preprocessor helps reduce bloat. Mixins can introduce bloat, and decrease bloat. 2. Clients should never edit the CSS. We've had folks claim that if we'd come up with the design, or even the template, and they'd use it. More often than not, they can't. They just don't know how to do it. The designs they want are just to complicated for them to edit the CSS to them. 3. Preprocessors do not introduce logic into the CSS, they introduce logic in how the CSS is created. By and large a normal site does not need any if/else/for-loop logic to the stylesheet. The problems that inspired jQuery, SASS, Less are all based upon inconsistent implementations. If the browsers would all just play along and implement all the standards we'd just be okay, right? But obviously you need compatibility layers to handle all the inconsistencies... and so you get frameworks, preprocessors, etc.