7 ms·

I've never found tailwind to help someone who isn't already a reasonably skilled web developer. If you don't know CSS tailwind gets your far enough sometimes, b

I've never found tailwind to help someone who isn't already a reasonably skilled web developer. If you don't know CSS tailwind gets your far enough sometimes, but you have to learn many of the same paradigms as you would in CSS and you can still create issues that aren't as simple as missing "text-green-500". Tailwind seems most useful for devs who don't want to be responsible for managing multiple CSS files and all the naming conventions that come along with it. They're basically looking for using inline styles after having likely heard for a long time to not use the style tag. For me at least, any value from tailwind went out the window when frameworks started leaning into single file components and scoped styles. I keep components small enough that generally my style selectors are only using element and attribute selectors, I dodge the class naming issue entirely and still get to use CSS instead of inline styles.

thiht 2mo ago
Well yeah, people need to learn the tools they’re using. How’s that shocking?
- bdangubic 2mo ago
  that ship has sailed loooong time ago, hence endless “why we stopped using _____” blogs that make the front page
- _heimdall 2mo ago
  It isn't shocking and that wasn't my point. The OP is pointing to benefits of tailwind related to onboaring new devs, I was just raising that doesn't match my experience. If a new dev doesn't know CSS well it won't help them. If a new dev does know CSS but doesn't know Tailwind, it still won't help. The standardization can be claimed as a benefit, though it really amounts to avoiding having to architect how CSS is managed in a project and at the end of the day the solution is to just inline styles one a time (I.e. no cascade or stylesheets). Though a bit unrelated, I take issue with the core promise of Tailwind - localization of styles on a node. As soon as flexbox and grid enter the picture I can't simply look at one node and know how it will render. Even more egregious is groups, though a useful feature it breaks locality of styling even worse. Throw in less used but valid syntax for attribute selectors, modifiers, sibling selectors, etc and you might as well be in CSS. Last I used TW it also didn't have an answer for using things like :has() though that could have changed.
janaagaard 2mo ago
> If you don't know CSS tailwind gets your far enough sometimes, but you have to learn many of the same paradigms as you would in CSS. This is also my experience. But one of my colleagues highlighted this as a strong feature. He had been doing web dev for many years, but always with a CSS framework. He was really glad that Tailwind forced him to learn plain CSS.

thiht 2mo ago

Well yeah, people need to learn the tools they’re using. How’s that shocking?

bdangubic 2mo ago
that ship has sailed loooong time ago, hence endless “why we stopped using _____” blogs that make the front page
_heimdall 2mo ago
It isn't shocking and that wasn't my point. The OP is pointing to benefits of tailwind related to onboaring new devs, I was just raising that doesn't match my experience. If a new dev doesn't know CSS well it won't help them. If a new dev does know CSS but doesn't know Tailwind, it still won't help. The standardization can be claimed as a benefit, though it really amounts to avoiding having to architect how CSS is managed in a project and at the end of the day the solution is to just inline styles one a time (I.e. no cascade or stylesheets). Though a bit unrelated, I take issue with the core promise of Tailwind - localization of styles on a node. As soon as flexbox and grid enter the picture I can't simply look at one node and know how it will render. Even more egregious is groups, though a useful feature it breaks locality of styling even worse. Throw in less used but valid syntax for attribute selectors, modifiers, sibling selectors, etc and you might as well be in CSS. Last I used TW it also didn't have an answer for using things like :has() though that could have changed.

janaagaard 2mo ago

> If you don't know CSS tailwind gets your far enough sometimes, but you have to learn many of the same paradigms as you would in CSS. This is also my experience. But one of my colleagues highlighted this as a strong feature. He had been doing web dev for many years, but always with a CSS framework. He was really glad that Tailwind forced him to learn plain CSS.