"Considering it’s a point of professional pride to avoid nested structures as much as possible in other languages..."
Nested loops can be bad. Nesting logic deeply in other languages is bad.
Nesting style rules that belong together, well, together isn't nesting as much as it is putting like stuff together.
I may create section.myawesomesection {...} and everything to do with the stuff in there is in there, not leaking out. I don't accidentally use a class name used somewhere else and globally change it, I don't change all global UL tags to be flat, inline, no list-style. I change them in context of section.myawesomesection.
Not to mention allowing me to put my breakpoints together in context (particularly useful with a mixin like breakpoint(small) or something).
Yes you can really go nuts with the nesting and create a giant pile of crap. But then that's you being a bad planner (not even going to say coder here, as CSS/SASS is more about planning than coding).
Nested loops can be bad. Nesting logic deeply in other languages is bad.
Nesting style rules that belong together, well, together isn't nesting as much as it is putting like stuff together.
I may create section.myawesomesection {...} and everything to do with the stuff in there is in there, not leaking out. I don't accidentally use a class name used somewhere else and globally change it, I don't change all global UL tags to be flat, inline, no list-style. I change them in context of section.myawesomesection.
Not to mention allowing me to put my breakpoints together in context (particularly useful with a mixin like breakpoint(small) or something).
Yes you can really go nuts with the nesting and create a giant pile of crap. But then that's you being a bad planner (not even going to say coder here, as CSS/SASS is more about planning than coding).