Tailwind suits the kind of developers who hack things together and build up technical debt and spaghetti code rather thinking about things first and designing things properly.
I don't know. In 20+ years I have seen way more abominations and spaghetti CSS using other every CSS technique.
With Tailwind at least I know what to expect, and the code in practice rarely deviates from what it's supposed to look like.
I'm all for "not building up technical debt" and "thinking about things first" but in my personal experience the anti-Tailwind crowd doesn't have much to show here in this regard. Sure: it's theoretically possible to build a perfect CSS ivory tower, I just haven't seen even a passable one in a non-trivial project, it always devolves into a mess for various reasons... often breaking the rules of the paradigms like BEM and OOCSS, often because of cutting corners here and there.
Addendum: I'm all for criticising techniques, but it's interesting that the anti-Tailwind crowd always resorts to attacking the character of the developers that use it.
I feel like it is the same with ORMs argument is always "they don't know proper SQL so they use ORM instead".
Which usually from people I know is they do know SQL and ORM and "no ORM crowd" doesn't have much to show.
Exactly the same with Tailwind, I see coworkers doing Tailwind and knowing CSS well and not being "pure vegan CSS developers".
But on the other hand we don't hire people who would utter such things like "no ORM" or "no framework" because those were also as in experience people who would create technical debt for others to deal with.
Same. Been doing this for 20+ years. I’ve worked at companies whose names are recognized and respected. My current Tailwind project is by far the most maintainable one I’ve worked on when it comes to CSS.
Hard disagree. Vanilla BEM + CSS produces a parallel component system that I find very unwelcome since React (or Vue/Svelte/etc.) already accomplishes this.
Tailwind removes this burden and helps you focus on writing actual React components when needed.
whstl|1 year ago
With Tailwind at least I know what to expect, and the code in practice rarely deviates from what it's supposed to look like.
I'm all for "not building up technical debt" and "thinking about things first" but in my personal experience the anti-Tailwind crowd doesn't have much to show here in this regard. Sure: it's theoretically possible to build a perfect CSS ivory tower, I just haven't seen even a passable one in a non-trivial project, it always devolves into a mess for various reasons... often breaking the rules of the paradigms like BEM and OOCSS, often because of cutting corners here and there.
Addendum: I'm all for criticising techniques, but it's interesting that the anti-Tailwind crowd always resorts to attacking the character of the developers that use it.
ozim|1 year ago
Which usually from people I know is they do know SQL and ORM and "no ORM crowd" doesn't have much to show.
Exactly the same with Tailwind, I see coworkers doing Tailwind and knowing CSS well and not being "pure vegan CSS developers".
But on the other hand we don't hire people who would utter such things like "no ORM" or "no framework" because those were also as in experience people who would create technical debt for others to deal with.
christophilus|1 year ago
robjn|1 year ago
Tailwind removes this burden and helps you focus on writing actual React components when needed.