When nesting is used incorrectly it's absolutely an anti-pattern (my first LESS project regrettably mimicked the HTML structure with nesting), but when everythi

When nesting is used incorrectly it's absolutely an anti-pattern (my first LESS project regrettably mimicked the HTML structure with nesting), but when everything is kept as semantic/modular as possible and nesting is avoided except where obvious (a UL class that styles the children LI/A tags, etc) it can be a great help in keeping your CSS simple and understandable. While it's more difficult to replicate the same issues in native CSS due to the friction involved of copying/pasting the same elements/classes over and over, I don't think that should be a reason to entirely avoid a tool that can be a great benefit in the long run. On the other hand, per our email I have to say I'm more and more skeptical of the benefit and long-term maintainability of SCSS @extends and @mixin except in special circumstances.