Sounds like we agree - you don't mean classes, you mean issues of cascading and specificity. See eg: https://alistapart.com/article/braces-to-pixels/ https://a

Sounds like we agree - you don't mean classes, you mean issues of cascading and specificity. See eg: https://alistapart.com/article/braces-to-pixels/ https://alistapart.com/article/braces-to-pixels/ for a brief overview / recap. The "other" options to utility/tailwind approach is to avoid classes, and use semantic html (easier in HTML5, where you can just decide you'll have an <article> with <lede> and <section>s) or heavily customized css classes (like bootstrap). Main difference between tailwind and bootstrap, is that bootstrap still assumes you'll have some container-elements that wrap other elements - while theoretically tailwind styles every element in isolation. (sort of)