Exactly! The basic argument of people like the post author is "Learn CSS, so you don't write shitty CSS". And in an ideal world he's right and I agree with him,

Exactly! The basic argument of people like the post author is "Learn CSS, so you don't write shitty CSS". And in an ideal world he's right and I agree with him, conceptually. The problem is where that ideal meets reality. Few developers bother learning CSS in depth to avoid spaghetti and poor practices, so whether we like it or not - that is a fact and a reality we have to deal with. That's solved by tooling and/or better languages and better abstractions - which is what css-in-js is aiming to do. Coding standards like naming conventions aren't enforceable enough to scale in real life :(.