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

Why Tailwind CSS Won

matt-rickard.com

Post reply on HN
Print view View original

101–110 of 559 posts

Re: Why Tailwind CSS Won

#101

Post by thrashh »

blowski wrote: post #24
fbnlsr wrote: post #11

I don't get Tailwind. In my book, CSS is here to facilitate the style of multiple webpages by modifying a set of rules, and classes are here to mutualise said rules. With Tailwind, it looks like you design by writing HTML, which is the opposite of what CSS aims at. So if you wish to change your design, you'll have to update multiple templates instead of one CSS rule. Every time I've had to work with Tailwind, it felt…

I can sum up what I like about Tailwind in the following code: ``` (in CSS) a.link { border: red; } a.link:hover { border: blue; } ``` ``` (in Tailwind) ``` It's much easier in Tailwind for me to see locally what's going on with that styling. If I lived in this code all the time, or I was good at structuring CSS, then maybe the first would be more appealing. But I'm a shit at CSS, it always turns into an unmaintainab…

That isn’t a Tailwind feature though? That’s been like a basic feature of CSS frameworks for 10+ years. Even Bootstrap was going this route way back when.

Who rolls the basic boring CSS classes like border-red or border-primary by themselves? People have been doing it for free for over a decade.

Re: Why Tailwind CSS Won

#102

Post by progx »

Wordpress, React, many others win too and nobody would say, that these are superior to anything else.

Like in WordPress or React you can fiddle with Tailwind too. People like to fiddle.

You can make things easy, or fiddle, what did people do? Correct, fiddle.

Why you think so many huge overbloated frameworks have soo much success. Fiddle. Fiddle is the key to everything in development.

You fiddle hours and hours until it works, you feel like the greatest dev on the planet.

You fiddle it, you write a blog post over your fiddle and how fun it was, other read it and fiddle too.

It work and they feel great too. Fiddle continues.

Re: Why Tailwind CSS Won

#103

Post by jjdeveloper »

surume wrote: post #66

According to NPM download stats, it has 6 million weekly downloads, the exact same amount as Styled Components. Emotion also has around 6 million. So that's 12 million for CSS-in-JS, as opposed to 6 million for Tailwind, so how did it win?

It’s still growing, those two others have flatlined or shrinking

Re: Why Tailwind CSS Won

#104

Post by Sander_Marechal »

chipgap98 wrote: post #94
xigoi wrote: post #52

Earlier quoted context omitted.

> Being able to think "Hmmm, I want a rounded button, with a border and a blue background" I rarely think this. It's usually “I want a button that looks like all other buttons on my site”. Vanilla CSS is great for that.

Tailwind is also great for this. You create components with Tailwind that make this trivial

Then you're just back at regular CSS with extra steps

Re: Why Tailwind CSS Won

#105

Post by [deleted] »

xigoi wrote: post #52
bennyp101 wrote: post #14

For getting designs up and running quickly, it really is great. Being able to think "Hmmm, I want a rounded button, with a border and a blue background" and just typing class="rounded border border-blue-600 bg-blue-500" and it's done. With lots of UI being components now, it doesn't really matter that it is verbose - I actually find that helpful. And even if you want to have a class that you use all over the place, j…

> Being able to think "Hmmm, I want a rounded button, with a border and a blue background" I rarely think this. It's usually “I want a button that looks like all other buttons on my site”. Vanilla CSS is great for that.

[deleted]

Re: Why Tailwind CSS Won

#106

Post by rjknight »

000ooo000 wrote: post #63

Silly premise and vapid article. Tailwind 'won' in the same way Bootstrap 'won', i.e. it was popular for a time. $10 says Tailwind will be the Bootstrap of 2027.

But this is how all victories work, whether it's a war or a sports competition or market share. You get to be the undisputed champion for a while, until eventually someone else comes along and beats you, or circumstances change so that your victory doesn't matter so much any more. "But Tailwind was only the dominant CSS framework for most of a decade" is not much of a criticism.

Re: Why Tailwind CSS Won

#107

Post by LtdJorge »

xigoi wrote: post #52
bennyp101 wrote: post #14

For getting designs up and running quickly, it really is great. Being able to think "Hmmm, I want a rounded button, with a border and a blue background" and just typing class="rounded border border-blue-600 bg-blue-500" and it's done. With lots of UI being components now, it doesn't really matter that it is verbose - I actually find that helpful. And even if you want to have a class that you use all over the place, j…

> Being able to think "Hmmm, I want a rounded button, with a border and a blue background" I rarely think this. It's usually “I want a button that looks like all other buttons on my site”. Vanilla CSS is great for that.

I assume OP means that for the fist button of the site, as in creating the site from 0.

Re: Why Tailwind CSS Won

#108

Post by fjfuvucucuc »

rpastuszak wrote: post #18

I think Tailwind is more accessible to many[*] less experienced or CSS-oriented developers. Big generalisation , I know, please don't yell at me, but many of us can get 99% of Tailwind's value with UI libraries supporting: 1) style encapsulation, 2) colocated presentation/content/behaviour and 3) a more minimalist mindset/habits when building UIs (e.g. relying on simpler styling hierarchies, native DOM elements, sema…

What's up with the colocation argument? Colocation of markup and business logic makes a lot of sense.

Colocation of presentation? Why do you even need that? Presentation is abstracted into CSS by design.

Having presentation decoupled allows you to abstract around visual elements on a page at their instead of having to sufficiently wrap everything in divs classes just to the right level to make the CSs classes work.

Re: Why Tailwind CSS Won

#110

Post by whazor »

000ooo000 wrote: post #63

Silly premise and vapid article. Tailwind 'won' in the same way Bootstrap 'won', i.e. it was popular for a time. $10 says Tailwind will be the Bootstrap of 2027.

That is the point. Tailwind is just CSS. And like the article says, you can copy paste designs from examples.

The key difference between Bootstrap and Tailwind is that Tailwind designs are distributed. So Bootstrap designs feel like Bootstrap designs, while for Tailwind you can keep having new and fresh designs from different sources.

Post reply on HN