HTML and CSS are just fundamentally not separate concerns anymore. I'm not sure they ever were. You cannot use CSS to turn a correct HTML document into any visu

HTML and CSS are just fundamentally not separate concerns anymore. I'm not sure they ever were. You cannot use CSS to turn a correct HTML document into any visual display without adding tags. The separation is an incorrect boundary. Any polemic toward Tailwind is incorrect if its basis is that the colocation is incorrect. Even less sensible is this "Tailwind's utility-first approach encourages developers to slap classes onto generic <div> and <span> elements, where semantic meaning is lost." No, it doesn't in any way. Class soup is a valid criticism, but apparently a lot of people fail to realize that tailwind is meant to be used with a component system. I don't think anyone serious is advocating for using tailwind while writing a big static document, copy pasting the button styles into each button. That would be stupid.