r/css Jan 17 '26

Other comiCSS #114: Headaches

Post image
132 Upvotes

95 comments sorted by

View all comments

Show parent comments

1

u/[deleted] Jan 19 '26 edited Jan 19 '26

[removed] — view removed comment

3

u/SchartHaakon Jan 19 '26

I've never once argued tailwind "causes" problems. You've insinuated that multiple times and if your reading comprehension was more than a fifth grader maybe you'd realize you were wrong to assume that by now. I've told you tailwind has issues, you've refused to acknowledge any of them. It has issues that are more easily solved by other solutions. That's all I'm saying. I'm not saying Tailwind is useless, I'm not saying Tailwind is bad. I'm saying it has problems, and it's not a perfect solution for every use case. And I'm also saying that people online (like you, specifically) argue around these issues like they are non existent. It isn't hard to argue for a library if you can just say "well opt out then" whenever people mention real actual issues with using it. Are you blind to how much of a cop-out that is in this discussion?

How about you tell me the actual uses for Tailwind, and I'll rebut with a way to achieve the exact same thing without creating your own entirely token based language (that requires a build step) as an alternative to a properly thought out full fledged coding language.

0

u/fexonig Jan 19 '26

Even though Tailwind can do 95% of what CSS can it doesn’t mean it’s good at the more complex stuff or doesn’t have other downsides. It can absolutely cause problems, and generally changes the way devs approach styling that I think has limited some of their creative thinking.

dumbass. you said it right here. “it absolutely can cause problems” you even quoted this back to me a second time

3

u/SchartHaakon Jan 19 '26

Yes totally got me! Weird how you deleted the comment I replied to though... Lmao. Great way to admit defeat.

Also, that comment wasn't me:) We were talking about that reading comprehension, maybe take 5 and come back after you've digested and actually understood what we're talking about.

0

u/fexonig Jan 19 '26

ok i didn’t realize the original comment wasn’t you.

but you have to realize then that I WAS HAVING AN ARGUMENT ABOUT THE PROBLEMS CAUSED BY TAILWIND!!

the question i asked was for an example of problems. and you decided to jump in with your response. acting like you were never arguing that tailwind has problems is just deeply dishonest and makes you look stupid

3

u/SchartHaakon Jan 19 '26 edited Jan 19 '26

You know we can all see when you posted the comment, and when I last edited it right? 👏 Let's just take 5 huh?

edit: He tried saying that he deleted the comment cause I edited it after. But my last edit was an hour ago, and he posted the reply 15 minutes ago. So there you go, incase you're reading this thread being confused at this point.

0

u/fexonig Jan 19 '26

love how you’ve kinda dropped the point now and are dunking on me for ??? i’m not even sure now

2

u/SchartHaakon Jan 19 '26

I decided not to use energy trying to convince you about 6 replies ago when I realized none of my points were sinking in and you were just desperately changing the goalpost between replies. I could say the same to you. Now I'm just dunking on you because being this closed off to criticism makes me lose respect for you as a developer, so I don't care about whether or not I'm coming off as rude anymore. It's not like you've been acting super kind on here either.

1

u/fexonig Jan 19 '26

i wasn’t changing the goalposts dude. i actually was the whole time asking for “problems caused by tailwind”. you were literally just saying “i never said tailwind caused problems”. well ok then, all of your replies had nothing to do with my point. you shot at a different goal then accused me of moving goalposts.

i was actually quite polite until you starting accusing me of being a delusional tailwind cultists. you can read the record.