> The commit will now contain 10000 non html structure changes to an html It's an acceptable trade off. Nothing is perfect. In exchange you're guaranteed those

> The commit will now contain 10000 non html structure changes to an html It's an acceptable trade off. Nothing is perfect. In exchange you're guaranteed those changes only affect this markup, and not some other li > ul > a whatever somewhere else. > Might as well go back to doing inline styles No, it is not. This has been explained thousands of times anyone says "tailwind is like inline styles". You can do responsive, you're limited to a consistent subset of rules, minimal output css file, caching, etc, etc. For example, here [1] is an explanation why it is not the same, but there are thousands. By reading your answers I deduce you've not used it yet. And this is exactly what is being discussed here. Fanatics closed inward looking people will never like it, nor anything that defies what they've been taught for years. Like religion almost. You have to try it for real to see the benefits. It is not perfect, but the net result is very positive for a lot of people as you can see from the usage statistics. Just be a bit more open minded to new tech and give it a try. At least you'll understand why it is not the same as inline styles which is a pretty basic thing you understand after 1 hour of using it. [1] https://frontstuff.io/no-utility-classes-arent-the-same-as-inline-styles https://frontstuff.io/no-utility-classes-arent-the-same-as-i...