"Nesting in Sass should be avoided" concurrently with "By doing this, a developer can see at a glance that .foo__baz {} lives inside .foo__bar {} lives inside

"Nesting in Sass should be avoided" concurrently with "By doing this, a developer can see at a glance that .foo__baz {} lives inside .foo__bar {} lives inside .foo {}." It's like reinventing descendant selectors, but with more typing. In fact, if descendant selectors weren't supported by browsers, this would be the workaround. And for the punchline, the authors suggest that "descendant" selectors (.foo__bar, etc) in plain CSS files should be indented additional spaces. Y'know, so they like the nesting in Sass that you're not supposed to do. (facepalm) OOCSS seems to combine all the ridiculous trends in computing into one bundle of sad: OO-fetishization, "don't do that because it takes a microsecond longer sometimes" premature optimization, and "hypothetical reusability trumps actual usability"...