News for hackers. Stuff that matters.
Re:Tailwind CSS v3.0 by drusepth on Thursday December 09, 2021 @08:14PM (#29505316)
To be fair, one of the big perks of Tailwind (IMO) is not having to have a big ol' folder of CSS that you have to figure out what applies where in HTML, but rather just having all your styling inline (while still staying consistent, which is the usual downside of inlining styles manually). Having to have a tailwind-addons.css when you needed random bits of CSS they didn't have classes for kind of sucked; this looks like a nice QOL that would get me back to the original goal of uniting structure-and-style into singular files.

FWIW, I also hated using header files in C++ and also wrote a Ruby library for inlining all my tests immediately following the functions they test. I like having more context when looking at code without having to flip around from file to file to piece a bigger picture together.

Re:Tailwind CSS v3.0 by docmars on Thursday December 09, 2021 @09:54PM (#29505927)
The same reason Vue introduced single-file components!

If you haven't tried Vue yet, I strongly recommend it based on what you said.

Re:Tailwind CSS v3.0 by drusepth on Thursday December 09, 2021 @11:13PM (#29506310)
Thanks for the recommendation! I've mostly been thrust into React, which works for what I need but I definitely don't enjoy it. I'll give Vue a shot!
Re:Tailwind CSS v3.0 by akvadrako on Friday December 10, 2021 @04:14AM (#29507968)
Svelte also has single file components.

It seems the biggest advantage most people find in tailwind is working around a react limitation.