4 ms·

> stop prentending it turns JS devs magically into css/html experts. It doesn't turn them magically into experts. It gives them the tools to implement complex

> stop prentending it turns JS devs magically into css/html experts. It doesn't turn them magically into experts. It gives them the tools to implement complex designs with relative ease, and it helps understand some deeper relationships and concepts in CSS. Speaking from own experience, YMMV and all that :)

robertoandred 6y ago
Not if they don't understand what those tools do or how to use them.
- aniforprez 6y ago
  I mean what's there to understand with tailwind? It's a bunch of CSS classes. You want to add a shadow to a button and the "shadow-md" class. Same with a ton of other things like border radius, text colour, padding etc
  - robertoandred 6y ago
    It's not about understanding or not understanding tailwind, it's understanding the CSS that it's applying for you. Tailwind is just a shortcut, you still have to know where you're going and why.
AltruisticGapHN 6y ago
> It gives them the tools to implement complex designs with relative ease The actual scenario is backend / js / "fullstack" devs can copy/paste from many available tailwind "blocks" such as a login screen and it "just works". They didn’t have to wrangle css imports, sass syntax, fugure out dependencies and such. In that respect tailwind is awesome for majority of devs who work without designs and asked to implement gazillions of admins, dashboards, dialogs, etc. I fully understand their position and the success of tailwind in that respect. Using eg. bootstrap is already several levels of complexity higher due to understanding where to put the css classes, why they break when you change the html structure, how to fix them, etc. Typical js devs can modify css but often they will do a hackjob, making the css worse. It’s as if they don’t have appreciation for how complex css is and that principles of software architecture CAN also apply incss such as low/high coupling. Much better if they have to "only" edit a template, better for everyone involved i. a team unles. they have a dedicated css expert. On my last professional project I was able to use both Sass and tailwind.. but even to do that requires solid understanding of css selectors specificity, css best practices, because by default tailwind classes and custom css will compete. So in my experience whether it’s tailwind or Sass code, non-css developers aren’t any better off when they are stuck with layout issues. They still assign the issue to the css guy ;) PS : with all that said I am grateful to tailwind as well as bem and SuitCSS for making me appreciate more the needs of the other guys on my team. Writing css / tailwind that doesn’t break easily and is more maintainable that’s the art and what makes me still love the "front of the frontend". Learning to appreciate tailwind which I disliked at first made me, a css expert (and very proficient in js as well) a better overall developer.
- balfirevic 6y ago
  > The actual scenario is backend / js / "fullstack" devs can copy/paste from many available tailwind "blocks" such as a login screen and it "just works". It's that, but also something more. Tailwind blocks are exact opposite of black-boxes. You can clearly see everything they are made of, tweak it and experiment with it in a fully localized manner. CSS imports and SASS syntax are the least of the problems Tailwind solves (I don't actually think they are problems at all).

robertoandred 6y ago

Not if they don't understand what those tools do or how to use them.

aniforprez 6y ago
I mean what's there to understand with tailwind? It's a bunch of CSS classes. You want to add a shadow to a button and the "shadow-md" class. Same with a ton of other things like border radius, text colour, padding etc
- robertoandred 6y ago
  It's not about understanding or not understanding tailwind, it's understanding the CSS that it's applying for you. Tailwind is just a shortcut, you still have to know where you're going and why.

AltruisticGapHN 6y ago

> It gives them the tools to implement complex designs with relative ease The actual scenario is backend / js / "fullstack" devs can copy/paste from many available tailwind "blocks" such as a login screen and it "just works". They didn’t have to wrangle css imports, sass syntax, fugure out dependencies and such. In that respect tailwind is awesome for majority of devs who work without designs and asked to implement gazillions of admins, dashboards, dialogs, etc. I fully understand their position and the success of tailwind in that respect. Using eg. bootstrap is already several levels of complexity higher due to understanding where to put the css classes, why they break when you change the html structure, how to fix them, etc. Typical js devs can modify css but often they will do a hackjob, making the css worse. It’s as if they don’t have appreciation for how complex css is and that principles of software architecture CAN also apply incss such as low/high coupling. Much better if they have to "only" edit a template, better for everyone involved i. a team unles. they have a dedicated css expert. On my last professional project I was able to use both Sass and tailwind.. but even to do that requires solid understanding of css selectors specificity, css best practices, because by default tailwind classes and custom css will compete. So in my experience whether it’s tailwind or Sass code, non-css developers aren’t any better off when they are stuck with layout issues. They still assign the issue to the css guy ;) PS : with all that said I am grateful to tailwind as well as bem and SuitCSS for making me appreciate more the needs of the other guys on my team. Writing css / tailwind that doesn’t break easily and is more maintainable that’s the art and what makes me still love the "front of the frontend". Learning to appreciate tailwind which I disliked at first made me, a css expert (and very proficient in js as well) a better overall developer.

balfirevic 6y ago
> The actual scenario is backend / js / "fullstack" devs can copy/paste from many available tailwind "blocks" such as a login screen and it "just works". It's that, but also something more. Tailwind blocks are exact opposite of black-boxes. You can clearly see everything they are made of, tweak it and experiment with it in a fully localized manner. CSS imports and SASS syntax are the least of the problems Tailwind solves (I don't actually think they are problems at all).