Live data from Hacker News

Tailwind Isn't for Me

spicyweb.dev

11–20 of 191 posts

Re: Tailwind Isn't for Me

#11

I'd actually love a tool that converts tailwind CSS to regular CSS on save because my biggest issue with CSS is that I constantly have to come up with ids and class names.

Tailwind to CSS: https://tailwind-to-css.vercel.app/ CSS to Tailwind: https://transform.tools/css-to-tailwind

Re: Tailwind Isn't for Me

#12
post #8

People want painkillers, not vitamins. That's why there is this endless flow of snake oil frameworks like Tailwind and all the others. People see some fancy demos and think "wow, so cool so easy" and "This is the newest framework, so it must be the best" and go for it. Then over time, they get caught in a web of problems that the complexity of the framework produces. Then a few people go for the vitamins route (plain…

In your analogy, wouldn't tailwind be more of a multivitamin, in that it contains a bunch CSS classes (vitamins) conveniently packaged and ready to go?

I haven't used tw yet, but I intend to because I was blown away by how much sense the authors' book Refactoring UI made.

Re: Tailwind Isn't for Me

#14

As someone who used to make websites in the myspace days (and has about that much experience with web dev, plus a few static client sites from high school), I gave tailwind a try for my most recent project. I think it saves me a bit of time, and it's easier to get a decent aesthetic quickly. That said, I don't feel it's strictly necessary, and I don't like the HTML bloating either. It makes me want to create classes,…

Imo, it's correct, assuming there isn't an automated conversion tool. Moreover, Tailwind has a bunch of confusing class names, and certain limitations (as in classes not being available).

Re: Tailwind Isn't for Me

#15
post #8

People want painkillers, not vitamins. That's why there is this endless flow of snake oil frameworks like Tailwind and all the others. People see some fancy demos and think "wow, so cool so easy" and "This is the newest framework, so it must be the best" and go for it. Then over time, they get caught in a web of problems that the complexity of the framework produces. Then a few people go for the vitamins route (plain…

It really depends, for most simple landing pages painkillers are just fine, I've also created extensive dashboards that were used 4-6 years without much iterations, then it's a waste to think too much about css structure. And clients are happy if it looks a bit sexy.

For a long-term project that will require lots of development a more thorough approach would be justified.

Re: Tailwind Isn't for Me

#16
post #2

Especially in the HTMX community I'm alwayws wondering why people are chosing Tailwind. I tried it too and had the same problems as stated in the article. Mainly that its polluting the HTML so much. I went the opposite route and am using PicoCSS now which works with semantic tags and can even work without any classes. Feels much cleaner

Locality of Behaviour:

"The behaviour of a unit of code should be as obvious as possible by looking only at that unit of code"

https://htmx.org/essays/locality-of-behaviour/

Some people want "cleaner" and that's fine, I much prefer things to be "right there" as much as possible. Must be how my brain works

Re: Tailwind Isn't for Me

#17
Tailwind is an abomination.

Of course it's easier to use. Pressing the bold button in MS Word is easier than setting up styles etc, but one makes it easy to create an impossible to maintain mess that could have been made by a primary schooler, and one makes it possible to create a consistent style that looks professional.

The only reason I think Tailwind is becoming popular now is it's exposing a bunch of things like rounded corners and drop shadows that are still cool but unlike Bootstrap you can slightly tweak your rounded corners easily. It'll still lead to everything looking the same, then people will probably ditch it and go back to really minimalist styles like HN to look cool again.

Re: Tailwind Isn't for Me

#19
post #12
post #8

People want painkillers, not vitamins. That's why there is this endless flow of snake oil frameworks like Tailwind and all the others. People see some fancy demos and think "wow, so cool so easy" and "This is the newest framework, so it must be the best" and go for it. Then over time, they get caught in a web of problems that the complexity of the framework produces. Then a few people go for the vitamins route (plain…

In your analogy, wouldn't tailwind be more of a multivitamin, in that it contains a bunch CSS classes (vitamins) conveniently packaged and ready to go? I haven't used tw yet, but I intend to because I was blown away by how much sense the authors' book Refactoring UI made.

Taking multivitamins is usually the wrong approach. So they are indeed a kind of snake oil.

Which condition do you intend to treat by taking multivitamins?

Have you looked at randomized controlled studies and found that they support your idea that taking MVs has a positive effect on that condition?

Have you got your bloodwork done? Did the doctor then suggest that based on your situation MVs are the right approach? I never have heard of such a thing happening.

So yeah, TW and MVs are similar. Both appeal to people who think "Hey, why do the work and figure things out and act appropriately? I can just swallow this magic pill!".

Re: Tailwind Isn't for Me

#20
post #8

People want painkillers, not vitamins. That's why there is this endless flow of snake oil frameworks like Tailwind and all the others. People see some fancy demos and think "wow, so cool so easy" and "This is the newest framework, so it must be the best" and go for it. Then over time, they get caught in a web of problems that the complexity of the framework produces. Then a few people go for the vitamins route (plain…

Just because something is old doesn’t mean it’s correct, this is such a curmudgeon take. Things we have have evolved over a long time, have been started hastily (JavaScript) and there’s no reason to believe we’re not in a local minimum and something much better is out there.

I personally believe the js model is completely wrong for the browser and something like an actor model would fit much better.

I’m not saying we should jump on every hype train, and personally really dislike the react ecosystem but I also think we should encourage exploring new approaches. CSS, html and js evolution is driven by the exploration of these new frameworks and they’re very different than what they were just a few years ago

Post reply on HN