It is clever in that half of it is missing: the componentisation that React (etc.) brings with it makes
this shine.
You can also define normal CSS classes based on the utility classes if you so wish.
Tailwind after 4 hours of learning
curve is so much nicer than cutting css or using old skool css frameworks. Some of that is because ready designed components exist that you can copy.
With an old skool css framework once you hit an edge case you can be snookered and spend ages diagnosing why because of some clever stuff they done.
Tailwind says “yeah css was a bad idea, let us abstract it away a bit” and does a nice job.
Yep but unfortunately the "classic" way of writing CSS does look equally awful after some time with multiple people on a larger project. The html is cleaner but the CSS becomes an awful mess.
The moment the first important! or inline stuff creeps into the page you are doomed. Utility frameworks feel a bit like giving up at the start and just rolling with it.
The major problem i see with these frameworks is that it is harder to maintain a consistent style across teams or even a few devs.
At least with a Tailwind attribute you know what you are getting.
A named CSS class can contain any definition and even if you are certain of those definitions, they can change depending on what the element is contained within.
You use refactoring/code structure techniques just like with regular code. Group stuff into components that belong together, use sensible names etc.
The cost of tailwind is that you do a bit of upfront work, when defining your design system/tokens in their config. The benefit is high default performance (css is less bloated) and high productivity because you tend not to switch to CSS/SCSS and get a natural DRYness from working with it.
I’ve used Tailwind in quite a few projects at this point. It’s a bit gross, yeah. But overall that’s a small price to pay for all the benefits it brings.
quickthrower2|3 years ago
Using a web framework? No.
It is clever in that half of it is missing: the componentisation that React (etc.) brings with it makes this shine.
You can also define normal CSS classes based on the utility classes if you so wish.
Tailwind after 4 hours of learning curve is so much nicer than cutting css or using old skool css frameworks. Some of that is because ready designed components exist that you can copy.
With an old skool css framework once you hit an edge case you can be snookered and spend ages diagnosing why because of some clever stuff they done.
Tailwind says “yeah css was a bad idea, let us abstract it away a bit” and does a nice job.
LordHeini|3 years ago
The moment the first important! or inline stuff creeps into the page you are doomed. Utility frameworks feel a bit like giving up at the start and just rolling with it.
The major problem i see with these frameworks is that it is harder to maintain a consistent style across teams or even a few devs.
andix|3 years ago
The huge benefit is, that you don’t split up HTML and CSS, you only write HTML.
jonwinstanley|3 years ago
A named CSS class can contain any definition and even if you are certain of those definitions, they can change depending on what the element is contained within.
dgb23|3 years ago
The cost of tailwind is that you do a bit of upfront work, when defining your design system/tokens in their config. The benefit is high default performance (css is less bloated) and high productivity because you tend not to switch to CSS/SCSS and get a natural DRYness from working with it.
cglace|3 years ago
danielvaughn|3 years ago
lloydatkinson|3 years ago
https://tailwindcss.com/#:~:text=Worried%20about%20duplicati....