Why Tailwind CSS Won
matt-rickard.com
Why Tailwind CSS Won
1–10 of 559 posts
Re: Why Tailwind CSS Won
#2Won what?
There are far better ways of writing CSS than Tailwind… take a look at Stephanie Eckles, Andy Bell and others work on how little CSS you actually need for great designs
Re: Why Tailwind CSS Won
#3Did it? What was its competitor?
Re: Why Tailwind CSS Won
#4Did it? What was its competitor?
[deleted]
Re: Why Tailwind CSS Won
#5I am a not-good-at-ui dev, meaning I _can_ build UIs pixel perfect if given some exact design files, but it is incredible hard for me to come up with things on my own. So whenever I build something that is not already defined fully by designers (like: most of the time), I have to use some UI component catalog like bootstrap and start assembling my UI based on the options there, at most I switch a theme file to something more fancy.
I basically was squarely the target group of bootstrap, and used it for lots of projects in all versions. I didn't actually care much about their technical progess (float, flex, css-grid, whatever), I just copypaste from the available widgets and add in my data.
Just LAST WEEK I learned that my favorite web framework (https://phoenixframework.org/) now ships with Tailwind preconfigured by default. I also heard good things about it from trusted colleagues. So, for the next big project I decided to jump in. Still I kind of have concerns: I need "typical components" like cards/tables/grid/... to be only a copypaste away; and I need to allow some designers be able to tweak the overall look and feel, roughly like a theming file where fonts/colors/... are defined at a single place. I hope it will be smooth after all these years of bootstrap and the "muscle memory" of how to compose pages with it.
Re: Why Tailwind CSS Won
#6It won in composability, readability and simplicity, it's resulting code and power usage is larger.
Re: Why Tailwind CSS Won
#7Won what?
For anyone who has been in web dev for long enough I can assure you there's nothing cleaner and more maintainable than avoiding CSS frameworks.
Re: Why Tailwind CSS Won
#8For me it won because I view tailwind as vanilla CSS with a nicer syntax (mostly) and sane defaults that makes your website look decent out of the box. With the prettier autosorting plugin, the classes are ordered in a predictable fashion, making it easier to read than one would imagine.
It's not a perfect replacement for vanilla CSS and I still fall back down to writing plain old CSS for stuff like box shadows or more interesting grid layouts, and using tailwind modifiers like different screen sizes is less than ideal with having to prefix every single CSS property with the same modifier.
Re: Why Tailwind CSS Won
#9Tailwind won because it didn't replace CSS, it added simplicity to it.
CSS + Tailwind will be my go-to stack for all my new projects.
Re: Why Tailwind CSS Won
#10I'm using Bootstrap in a Tailwind kind of way, with many utility classes. I don't use it's container system.
How do you get a basic Tailwind design running? It seems like you need a Bootstrap equivalent on it anyway.