News for hackers. Stuff that matters.
Re:What working with Tailwind CSS every day for 2 years look... by adwww on Tuesday November 29, 2022 @12:21PM (#33790364)
I'm not super up to date with frontend development trends, but when I used it recently it really went against everything I've ever been taught about separation of concerns.

Like, I thought we were supposed to keep our content and styles separate, not mismatch them all together with a thousand utility class imports.

Re:What working with Tailwind CSS every day for 2 years look... by naasking on Tuesday November 29, 2022 @02:19PM (#33791900)
Consider whether those lessons were actually informed by evidence. Tailwind is not like inline CSS, the latter has a number of downsides because it doesn't permit you to access all of CSS, where Tailwind does.
Re:What working with Tailwind CSS every day for 2 years look... by atsjie on Tuesday November 29, 2022 @02:32PM (#33792081)
This has changed a number of years ago.

Basically it's a component-mindset; create some file with everything in it so that in the rest of the app you can just use `<MyButton>...</MyButton>`.

The `<MyButton />` file takes responsibility for everything it does (logic, handlers, markup, style).

However; this does not mean these files should grow large. Instead when things become too big (say over 250 LoC) you split up responsibilities by sub-components.

It's basically dividing problems in ever-smaller problems, but NOT by separating by technology (html/css/js).

Separation of concerns is horizontal slicing of the app architecture, components however slice the architecture vertically.