I wasn't attacking sass either, I've got large projects in production with both approaches. I was countering the point that it's 'impossible' or 'unreasonably hard' as someone else put it to write maintainable CSS code, which is absolutely ludicrous. Like I mentioned, CSS is included in more easy to maintain apps in production than almost any other language in existence. Sure, it's in a lot of code salads too, but that's beside the point, because OP's point was that Sass is somehow mandatory because software engineers can't be trusted to write clean code without it.
The original phrasing was "at scale". I'm only talking about sites with more than a dozen components and/or pages. At my job we have hundreds of components, some of which are used in hundreds of contexts, and we would have an insane time avoiding style leakage without nested selectors.
