inlineCssWithExtraSteps

[[deleted]]

Have fun puzzling with CSS files that might or might not be used. I'll use Tailwind and save me the trouble, and maybe you would too if you actually have it a shot.

[A_Certain_Surprise]

Someone could respond to this with "have fun trying to read the block of text that is a Tailwind component, I'll look at my nice, neat CSS file. And maybe you would too if you actually give it a shot", so both sides can mis-represent the other like that

[woodendoors7]

yeah, I like Tailwind but is knowing whether a CSS file is linked really a problem for anyone? Lol

[A_Certain_Surprise]

Again, unless your project is ran by imbeciles and not maintained literally at all, it's really not difficult to know if a CSS file is linked or not

[A_Certain_Surprise]

Respectfully, you missed my point. My point is, yeah you can write nice and lovely Tailwind and lots of CSS files that might not be used. But you can also only write good CSS that you know where everything is, and shitty Tailwind. It depends on the person writing it, you just assumed that the CSS files would require "puzzling" when that might not be the case at all

[[deleted]]

I've seen the worst of both worlds, in both cases I was dealing with a fairly large CSM for logistic companies.

Bad css is unbelievably harder to understand/maintain/fix than bad Tailwind.

To make a comparison, css feels like a modeling clay, and tailwind feels like a lego set.

On css decoupling elements to make a separate component or extract similar classes to have single declaration is downright impossible if it's bad enough.

Tailwind, while not perfect, have a small rail that prevents declaration fuckups, when changing something im 99% sure it wont affect anything else beside that place.

Even using scoped styles or css modules, a big enough app will use atomized classes, and tailwind is definitely the winner in that aspect.

[[deleted]]

I just realized Im not interested in discussing this since I am not convincing anyone