Live data from Hacker News

DaisyUI – Tailwind CSS Components

daisyui.com

81–90 of 174 posts

Re: DaisyUI – Tailwind CSS Components

#83
We've gone full circle - CSS components to inline CSS-in-HTML back to CSS components.

But I actually think I will use this. A big problem with CSS is that you end up making overrides no matter how composable you make the classes. And some simple things (e.g. responsiveness) are unintuitive and / or annoying to do in CSS. Hence Tailwind's "CSS-in-HTML" mini classes. But that doesn't fill the core purpose of CSS, bigger general-purpose classes to avoid repetition. Combine the two (general classes + mini classes for slight case-by-case fixes) and you get the best CSS experience I've seen so far (at least I think, I haven't tried it yet).

Re: DaisyUI – Tailwind CSS Components

#84

Very welcome. Sometimes the amount of classes needed in Tailwind is enormous. I paid for the TailwindUI pack too. But as nice as Tailwind is, the guys who built TailwindUI don't really get or understand a lot of real-world design patterns. A lot of stuff in there is needlessly complicated. Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness. Overuse of flex for…

>>>Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness.

I have to agree with this.

Re: DaisyUI – Tailwind CSS Components

#86
post #27

Earlier quoted context omitted.

But if you're going to hide away CSS inside a component, why not just use inline CSS? What does Tailwind add to this?

a very underrated feature of Tailwind is it's excellent documentation with immediate search. Want italic text? In straight CSS, how long will it take to look up is it font-style: italic; or text-style: italic or text-italic: true ? Tailwind's docs make it virtually instant. Even more impressive with flex and grid layouts (is it justify-items or align-items, etc). I find that Tailwind reduces the time from "idea in br…

This is the worst "feature" ever.

What's the point in spending 20 hours learning some custom interface that's only used in like 5% of projects and will probably be gone in 5 years, when you could spend 30 hours learning the standard that's been around for decades and understand every library for years to come?

Just learn CSS, it's not that hard.

Re: DaisyUI – Tailwind CSS Components

#87
post #29

Interesting side effects of css utility frameworks: I was trying to scrape a website that uses tailwind this week and it’s really difficult, as nothing had a unique class name.

That's not very nice, maintainability suffers in the same way. You can obfuscate your classes later on.

But alas, the battle for semantic css has already been lost and the community keep going in the opposite way (first bootstrap, which was halfway through, now tailwind which is basically inline styles with variables).

Post reply on HN