> Switching to a CSS file to change styles is a costly context switch
It is?! I have an IDE with more than one pane. CSS-in-JS exists if you really don't want to switch (albeit with its own problems)
> you can just copy and paste a list of classes or an HTML block into your application
Well back in my day we called these "inline styles" and came with their own problems. CSS is copy-pastable as well, and easily composed with classes.
> Compare this to [..] CSS build systems like Saas
Tailwind requires a build step! Frankly, I haven't seen a sizeable webapp without a "build step" for incorporating even plain CSS
> The best way to write the least amount of CSS is to just compose basic styles
This feels like an argument against Tailwind? Utility classes are helpful but will never be enough to replace CSS entirely without long lists of classes on every element
> Switching to a CSS file to change styles is a costly context switch
It is?! I have an IDE with more than one pane. CSS-in-JS exists if you really don't want to switch (albeit with its own problems)
> you can just copy and paste a list of classes or an HTML block into your application
Well back in my day we called these "inline styles" and came with their own problems. CSS is copy-pastable as well, and easily composed with classes.
> Compare this to [..] CSS build systems like Saas
Tailwind requires a build step! Frankly, I haven't seen a sizeable webapp without a "build step" for incorporating even plain CSS
> The best way to write the least amount of CSS is to just compose basic styles
This feels like an argument against Tailwind? Utility classes are helpful but will never be enough to replace CSS entirely without long lists of classes on every element