I don't think this is specifically a react problem. The problem is that people don't want to learn what modern CSS can do, or write it themselves (see Tailwind), and most new frameworks make it easy to just sidestep that with div soup.

Some of us _like_ CSS, and try to use as much of it when possible, but I feel like we are few and far between. I use react to manage the state of my app, but that doesn't mean I have to make a 27 div component to style an input.

The big problem is trying to convince the rest of the team that they should learn and use CSS.

▲

stavros 3 hours ago | parent | next [-]

I really don't understand Tailwind. I heard great things about it, and then I tried it and it seemed like setting style="" on all elements, but with extra steps.

Did we go off semantic CSS and returned to setting properties on each element, or was I using it wrong?

	▲	shimman 38 minutes ago \| parent \| next [-]
		You aren't using it wrong, the only thing tailwind does better than 99% of devs is having default values that both look nice and mesh together well. Utility based CSS has been around as long as classes have, tailwind is just one iteration of that. GitHub use to have a utility css library as well before switching to their new design.
	▲	an0malous an hour ago \| parent \| prev \| next [-]
		CSS is a little too low level for most web app design, Tailwind is a bit higher level and more concise than its CSS equivalent. It also has a bunch of sensible defaults for colors, sizes, spacing, and type.
	▲	sorahn 3 hours ago \| parent \| prev \| next [-]
		If you're experienced with or like the way CSS works, and you didn't like Tailwind, then you were probably using it correctly.
	▲	mhitza 2 hours ago \| parent \| prev [-]
		> and it seemed like setting style="" on all elements, but with extra steps. And extra benefits. Generally more concise on the common usecase, but more importantly you can combine and use media queries, which can't be done with inline styles alone.

▲

rahoulb 4 hours ago | parent | prev [-]

I agree it's not just React - I think a lot of people simply do not know what CSS can do nowadays.

I do like Tailwind (I guess it fits with how I think). But to make good use of it you _do_ need to know how CSS works (for example, using variant selectors for picking out child elements, using container queries instead of global breakpoints etc).

One addition - I learnt a _lot_ about CSS by reading [Every Layout](https://every-layout.dev/).