5 ms·

I have to chuckle a little at these posts that seem to be 'upset' that Tailwind (or some new framework du jour) is not the silver bullet that the hype train has

I have to chuckle a little at these posts that seem to be 'upset' that Tailwind (or some new framework du jour) is not the silver bullet that the hype train has had them believe I love Tailwind and use it daily, have done for almost 6 years now and I haven't experienced any issue I couldn't solve It certainly has never got me thinking to just throw it away or denigrate it publicly. And my solutions have worked well in a team setting - not adding any burden to other devs This feels more like it's at the intersection of React-specific problems and lack of experience with Tailwind and/or CSS in general I can see some of these problems being frustrating, but because the author seems to just be sounding off without much effort to express attempted solutions, I'm flagging because I feel like this is just anti-Tailwind inflammatory BS Edit: Title also needs to indicate this is from 2021

redbar0n 4y ago
> but because the author seems to just be sounding off without much effort to express attempted solutions, I'm flagging because I feel like this is just anti-Tailwind inflammatory BS On attempted solutions, there was a subsection titled: "What should I use instead of Tailwind for my design system?" He also suggested this solution for Tailwind, if you read it carefully: "If you still like what Tailwind offers, I recommend a similar approach that we do at Draftbit. Create a tiny layer on top of it: Treat all the Tailwind tokens as code and maintain Tailwind scoped inside those components. Abstract those utility components that you found repeated in your code into a more strict version, and minimise Tailwind for your app." The post was arguably not inflammatory, but pointed to specific issues with Tailwind viz-a-viz design systems. The points raised may not be correct(?), but that doesn't mean it's inflammatory BS. > Edit: Title also needs to indicate this is from 2021 Good point. Updated.
- pvg 4y ago
  Updated. You don't need the month, the HNconvention just uses the year in parens and some things rely on that format.
- simonhamp 4y ago
  I said "I feel like"... that's just how reading the article made me feel I think if it was really intent on providing a clear argument, the author would have gone to a little more trouble to show their work and taken us all on the journey As they didn't, I'm not convinced, and the fact that it's made its way to the top of HN suggests there's just a bunch of anti-TW up-voters ready to jump as soon as there's a whiff of some apparently-new reason not to use it Kinda disappointed this article got shared again tbh
deleted 4y ago
[deleted]

redbar0n 4y ago

> but because the author seems to just be sounding off without much effort to express attempted solutions, I'm flagging because I feel like this is just anti-Tailwind inflammatory BS On attempted solutions, there was a subsection titled: "What should I use instead of Tailwind for my design system?" He also suggested this solution for Tailwind, if you read it carefully: "If you still like what Tailwind offers, I recommend a similar approach that we do at Draftbit. Create a tiny layer on top of it: Treat all the Tailwind tokens as code and maintain Tailwind scoped inside those components. Abstract those utility components that you found repeated in your code into a more strict version, and minimise Tailwind for your app." The post was arguably not inflammatory, but pointed to specific issues with Tailwind viz-a-viz design systems. The points raised may not be correct(?), but that doesn't mean it's inflammatory BS. > Edit: Title also needs to indicate this is from 2021 Good point. Updated.

pvg 4y ago
Updated. You don't need the month, the HNconvention just uses the year in parens and some things rely on that format.
simonhamp 4y ago
I said "I feel like"... that's just how reading the article made me feel I think if it was really intent on providing a clear argument, the author would have gone to a little more trouble to show their work and taken us all on the journey As they didn't, I'm not convinced, and the fact that it's made its way to the top of HN suggests there's just a bunch of anti-TW up-voters ready to jump as soon as there's a whiff of some apparently-new reason not to use it Kinda disappointed this article got shared again tbh

deleted 4y ago

[deleted]