429
[ComiCSS] Benefits of Tailwind
(files.catbox.moe)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Jun 2025
429 points (97.8% liked)
Programmer Humor
25374 readers
1834 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I was very much against frameworks initially: tailwind, bootstrap etc. However, when I started really building sites & apps using components, I found tailwind made my life a lot easier, so I could easily see and change styling while writing code/html, and it would only affect that component.
Beforehand, I was trying to come up with names for CSS classes all the time, and then I'd change one thing, and fuck up styling on a diff page.
Honestly love tailwind. Once you get used to all the names/abbreviations and how they work with sizes and states etc. it's much easier to see what's happening when eyeballing code.
Makes reviewing and bug fixing easier too.
I get that early on it feels annoying. I recall disliking it the first time I learnt it, but then when I went back to regular css and classes I really missed it.
Now it is remembering tags for property instead.
Except that you learn the class names once and re-use them across all your projects, whereas CSS classes are different for every single project.
Any passable editor nowadays does the heavy lifting for you, you can usually even write the CSS tag you want and it'll show you the options.
Yep, a component is a good abstraction level, no point in making life difficult by creating and coming up with names for smaller parts.