Is CSS pleasant in teams of fullstack (not CSS specialists)? Not in my experience. It becomes a maze of Chesterton's fences.

▲

azangru 18 hours ago | parent [-]

I would have understood if tailwind got popular primarily among full-stack or backend developers: people who have neither time nor interest to learn CSS deeply. But, what contradicts this expectation is that one still needs to acquire CSS knowledge to use tailwind, and that some front-end developers seem to prefer it as well. Although I still cannot tell whether there are more front-end developers who prefer tailwind over plain CSS than the other way around.

▲

hahahahhaah 17 hours ago | parent [-]

I was too subtle but the issue is less understanding CSS and more collaborating in a team where someone decides to add a specific rule that fixes something applies on every page but makes no sense semantically.

Then do that 100 times to create spaghetti. CSS rule anywhere can affect anything whereas tailwind is more local.

You can also bricklay it along lines of components in React, so you know how X component renders always and it wont look like a pig when tranplanted to the legacy billing screen.

I now recall why I like tailwind! Been backending for a while now (zero regrets lol)

▲

cluckindan 17 hours ago | parent [-]

The irony is that Tailwind is not semantic at all.

▲

hahahahhaah 15 hours ago | parent [-]

Thats not irony so much as the reason. BYO semantics (using React most likely)

It is style assembler.

	▲	cluckindan 6 hours ago \| parent [-]
		It is horrible and I would never choose to use it.