The hardest part about programming is naming things. If you use tailwind you don’t have to name things.
That’s why it won.
Why Tailwind CSS Won
31–40 of 559 posts
Re: Why Tailwind CSS Won
#32Lol, who ever said it won? Paid HTML components? Get over yourself.
Heck people can even come together for a web framework let alone one tiny paid CSS tooling.
Re: Why Tailwind CSS Won
#33Re: Why Tailwind CSS Won
#34I 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…
> So if you wish to change your design, you'll have to update multiple templates instead of one CSS rule.
Changing the CSS to apply site-wide changes sounds great in theory but after working in front-end since IE6, this almost never happens in practice. You're never certain how the styles cascade and indirectly affect things so you're afraid of changing the core CSS.
Styles isolated to components is a much more scalable approach in my opinion and then it doesn't really matter whether you use Tailwind, CSS-in-JS or scoped CSS (Vue etc).
Re: Why Tailwind CSS Won
#35I 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…
> if you wish to change your design, you'll have to update multiple templates instead of one CSS rule. this comes up on every tailwind post and it isn't true. tailwind encourages you to not repeat yourself by making reusable components (or fragments etc) instead of reusable classes. that way if I want to see how the button both looks and works I only have one place to look even if you don't do this, with tailwind you…
I don't feel this point is strong because when you look at some of the most popular Tailwind components or templates in the ecosystem, such as the one made by the Tailwind people, the Tailwind code is still pretty crazy.
Re: Why Tailwind CSS Won
#36Once again, the "write once lots of small websites" people and the "maintain huge web apps" people, will be talking past each other. We share a base layer in HTML, CSS, JS, but the incentives, requirements, job environments, team sizes, couldn't be more different. I wonder about other languages and ecosystems. What would be a similar situation for e.g. C? Is there such a thing?
Well, the reason those web apps are huge might not be what you think.
Re: Why Tailwind CSS Won
#37I 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…
In my understanding it somehow abstracts the process of styling a website or whatever and make it easy for people who for any reason don't want to write CSS. Although I have the sensation many people find hard to write CSS and even despise it (I've read people here in HN who seem to think we should've kept doing layouts with HTML tables and don't agree layout is the job of CSS!) I definitely agree having dozens of cl…
Tailwind gives something like a fluent interface.
div.height(maxVH).color(primary).hide()
It’s all stuffed in classes because that’s the limitation given and this information belongs in the markup.
The above is much cleaner to me than: div.class(“primary”). I need to go find primary. What is the parent class. What happens if this isn’t a div now etc. what happens if the parent isn’t a div?
Tailwind just spells it out for you right alongside the layout so that you have all the information in one place.
For me personally, I was able to do things in tailwind I could never do in raw css, but I bet I got better at css as a result.
The docs are also incredible for tailwind. As good as mdn is, you need to already know what you’re looking for.
Re: Why Tailwind CSS Won
#38Re: Why Tailwind CSS Won
#39Re: Why Tailwind CSS Won
#40The whole "Why _____ won" is the same as specific politically affiliated news channel trying to sway future voters by stating some inflated Exit Poll numbers in favor of the party they are trying to portray as winning the election. Same reason why you see every new graduate you see has been affected by the whole MongoDB/NoSQL, React propaganda.