Here's a great talk on why he asserts that: https://www.youtube.com/watch?v=J_7_mnFSLDg
Not sure I 100% agree, but I appreciate the fresh look at oil patters.
Each class is applied in pipeline.
And ONLY to that tag. This is key. This leads to know, exactly, what are the effects on each tag, making the UI design very readable.
Then, you can customize it, and have a way to generate a VERY small CSS as result (another big advantage!) because the naming is normalized.
In short: Is the "same" but with more structure, predictability and tooling applied.
The more you need to customize, and the more pain you to "reverse" a CSS made by others, the more this make sense.
Half of TailwindCSS is a _way_ of using styles, but the other half is almost a theme: a set of margins, paddings, text sizes, colours, etc. that work well together.
Everything is now all at the same global namespace and all of the issues that people run into with specificity go away in the process.
It’s not my personal choice on how to solve that problem I think shadowDOM via web components are a much nicer option personally but Tailwind has a lot of very enthusiastic fans who seem to enjoy it.