Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tailwind Isn't for Me

spicyweb.dev

Post reply on HN
Print view View original

21–30 of 191 posts

Re: Tailwind Isn't for Me

#21

Post by TekMol »

mstipetic wrote: post #20
TekMol wrote: 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…

Evolution is very hard to beat.

CSS is not static. It has been getting better and better all the time and keeps improving.

Re: Tailwind Isn't for Me

#22

Post by rimliu »

nomilk wrote: post #12
TekMol wrote: 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.

CSS classes in this case are microplastics, not vitamins.

Re: Tailwind Isn't for Me

#23

Post by tipiirai »

PUSH_AX wrote: post #10

I love tailwind. I strongly feel that most modern CSS solutions are massively overthought. In engineering we have bigger problems to solve than a key/value list that makes a div blue. Tailwind removes the thinking around CSS, naming, preprocessors etc etc, it just lets me write good CSS and focus on components and other engineering problems. I seem to be one of the few people who can read CSS properties horizontally…

Curious: which modern CSS solutions are you referring to?

Re: Tailwind Isn't for Me

#24

Post by mapreduce »

> We live in a world where custom elements (aka ) are fully supported and enabled by modern browsers.

Don't we need to define the custom element using javascript first?

All my knowledge about custom elements comes from this Mozilla doc: https://developer.mozilla.org/en-US/docs/Web/API/Web_compone...

If custom elements is the way to go, it sounds like a lot of javascript and coding overhead that I have to take. Doesn't it?

Re: Tailwind Isn't for Me

#25

Post by dbbk »

PUSH_AX wrote: post #10

I love tailwind. I strongly feel that most modern CSS solutions are massively overthought. In engineering we have bigger problems to solve than a key/value list that makes a div blue. Tailwind removes the thinking around CSS, naming, preprocessors etc etc, it just lets me write good CSS and focus on components and other engineering problems. I seem to be one of the few people who can read CSS properties horizontally…

Why not Styled Components? I've been using them for years now and I'm extremely productive.

Tailwind on the other hand looks like a hellish nightmare, horizontal reading, proprietary syntax, no selector targeting of other components.

Re: Tailwind Isn't for Me

#26

Post by klysm »

jack_riminton wrote: post #16
geek_at wrote: 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

Unfortunately it’s a little more complicated than locality of behavior because there is a trade off with duplication and consistency of behavior

Re: Tailwind Isn't for Me

#27

Post by Ennea »

weinzierl wrote: post #4

This from 2021. No criticism, it is a good post. I was just confused at first and only realized it when I came about the part mentioning the JIT. This is a hill I will die on: Blog posts should have a date at the top.

I will be sharing that hill with you, if you don't mind.

Re: Tailwind Isn't for Me

#28

Post by miohtama »

I use Svelte for frontend develoment, and used all of JS frameworks that came before it. It's very web component'y. I feel Tailwind was partially created by the problems rising from the bad design choices of many modern web frameworks.

In Svelte, There is less need to use Tailwind, because HTML, CSS and JS (or TS) are all encapsulated in a single source file. Editing CSS alongside the HTML is easier than bloating the HTML with a class hell. You can use native syntax highlighting, IntelliSense, early compiler error catching and linting plugins of your editor.

Re: Tailwind Isn't for Me

#29

Post by ellinoora »

PUSH_AX wrote: post #10

I love tailwind. I strongly feel that most modern CSS solutions are massively overthought. In engineering we have bigger problems to solve than a key/value list that makes a div blue. Tailwind removes the thinking around CSS, naming, preprocessors etc etc, it just lets me write good CSS and focus on components and other engineering problems. I seem to be one of the few people who can read CSS properties horizontally…

My biggest issue with Tailwind is point #5 on the article: Tailwind encourages div/span-tag soup. Together with the class name soup my HTML becomes unreadable.

Re: Tailwind Isn't for Me

#30

Post by PUSH_AX »

tipiirai wrote: post #23
PUSH_AX wrote: post #10

I love tailwind. I strongly feel that most modern CSS solutions are massively overthought. In engineering we have bigger problems to solve than a key/value list that makes a div blue. Tailwind removes the thinking around CSS, naming, preprocessors etc etc, it just lets me write good CSS and focus on components and other engineering problems. I seem to be one of the few people who can read CSS properties horizontally…

Curious: which modern CSS solutions are you referring to?

For example, styled components, stylex etc.
Post reply on HN