1. 15
  1.  

  2. 9

    In my last day job, I suggested removing all instances of LESS. Not because it’s bad, or because Sass is “better” in some way.

    I suggested removing it and not replacing it with Sass, instead keeping with plain CSS, because I felt the team had not shown the discipline to not abuse the extra power a pre-processor gives you.

    The codebase was a tangle of nested rules which results in overly complex and specific selectors. When specifics of those need to change, the team doesn’t back out of the existing specificity, but instead overwrite it with more. Add to this a liberal helping of mixins — because “code reuse”, apparently — and the resulting CSS is applied, disabled, reapplied, over and over.

    My suggestion to not use a pre-processor was met with exasperation: “But everyone uses pre-processors! Every professional company uses them. That’s just the way it’s done!”

    I think the benefits of pre-processors don’t outweigh the drawbacks, especially in the hands of the enthusiastic but inexperienced. Plain CSS gets you plenty far enough. That said, I’m not sure about using some of the rules shown in the parent article — I’m not convinced browsers support them completely the same just yet. I’d rather stay off the bleeding edge of CSS.