Coming to Terms with Tailwind
johanronsse.be
Coming to Terms with Tailwind
1–10 of 117 posts
Re: Coming to Terms with Tailwind
#2Congratulate to the author. At this day, it takes quite a bit of self-awareness to be able to look at some previously (openly published) opinions, reconsider them, and admit that the opinion changed.
Re: Coming to Terms with Tailwind
#3Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
Re: Coming to Terms with Tailwind
#4Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
Have you tried it? I don't know what you mean by "sign of dementia", but I find the approach taken by tailwind makes me a lot more successful in applying designs. Doesn't feel like dementia to me.
Re: Coming to Terms with Tailwind
#5Congratulate to the author. At this day, it takes quite a bit of self-awareness to be able to look at some previously (openly published) opinions, reconsider them, and admit that the opinion changed.
He never said that his opinion changed. He just said that he accepted that Tailwind is now part of the frontend dev landscape (for better or for worse, time will tell), and tried to name some good parts of it.
Re: Coming to Terms with Tailwind
#6I don't know how Twitter works exactly but if I was using it for promotion I'd probably block the negative nancies from piggy backing on my posts if I could too.
Anyway, I think the tooling around Tailwind (at least in React/next) has gotten much better since the author wrote his initial criticisms AND tailwind is even more ubiquitous now-- which for better or worse makes it more acceptable even if some of the CSS mappings change over time. We put up with that sort of problem with JS as a matter of course so maybe my attitude is too blasé on that point though.
Re: Coming to Terms with Tailwind
#7Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
After years of wrestling with what the “right” UI framework was and marrying your project to the syntax and rules, Tailwind has entirely removed that concern from my life.
Re: Coming to Terms with Tailwind
#8Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
Have you tried it? I don't know what you mean by "sign of dementia", but I find the approach taken by tailwind makes me a lot more successful in applying designs. Doesn't feel like dementia to me.
If I go to it and it has react-specific crap all over it, I hit the back button
Re: Coming to Terms with Tailwind
#9Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
This is the thing, not all projects are super giant web applications being maintained by hundreds of front-end developers. For a dummy like me who curses at the laptop every time he needs to center a div and whose style sense pretty limited, tools like tailwind are a bless. I do a small library of components, copy what people who knows more than me does (taking examples from here https://tailwindcomponents.com/) adapt them to my needs and that's it. I dont have neither the skills, nor the time or the inclination to spent time on other alternatives. I like the style (more than bootstrap) and I am willing to pay the price of a cluttered html.
Re: Coming to Terms with Tailwind
#10Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.
Slightly less typing (compared to CSS), pre-defined memorable names, good documentation and a library of examples.
It's just convenient, that's it. Ideologically I don't like it; for getting work done, it's nice.
Theoretically you could achieve much of it in a "more correct" way, but we don't have the resource to do that in our company and ultimately it wouldn't be much of a value-add. Tailwind saves time.