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

DaisyUI: Tailwind CSS Components

daisyui.com

Post reply on HN
Print view View original

11–20 of 181 posts

Re: DaisyUI: Tailwind CSS Components

#11

Post by savanaly »

jug wrote: post #5

Doesn't this miss the point with Tailwind and why we have Tailwind in the first place?

>Doesn't this miss the point with Tailwind and why we have Tailwind in the first place?

Not for me. Say I have a new app and I want it to have a left nav. I could write my own styles with tailwind or...I could just put a .menu on there and gets all the sensible defaults for padding, spacing, font size, background colors, etc.

But having done that, I'll still want to edit the specific padding, spacing, fonts, and background color of the menu to suit my needs. Plus there's...the whole rest of the site, not all of which is made up of DaisyUI components. So I will be wanting Tailwind for all that for the regular reasons one wants Tailwind.

Re: DaisyUI: Tailwind CSS Components

#12

Post by k__ »

sudhirj wrote: post #10

This is a rebuild of the antithesis of Tailwind on Tailwind. Bootstrap had this for decades (Daisy even copies the same semantic class names in some cases). Tailwind was supposed to break away from this, to specific actual styles directly, but looks like we're coming back full circle again. Why not just use Bootstrap?

Maybe Tailwind has better dead code removal.

Re: DaisyUI: Tailwind CSS Components

#14

Post by 65 »

sudhirj wrote: post #10

This is a rebuild of the antithesis of Tailwind on Tailwind. Bootstrap had this for decades (Daisy even copies the same semantic class names in some cases). Tailwind was supposed to break away from this, to specific actual styles directly, but looks like we're coming back full circle again. Why not just use Bootstrap?

Because you can use Tailwind on top of DaisyUI, e.g. `btn rounded-lg`

Re: DaisyUI: Tailwind CSS Components

#15

Post by WesolyKubeczek »

I don’t know, it’s like you ask me to use CSS as it meant to be used all along, I don’t understand why I would need tailwind with daisy on top if I could just write CSS with the added benefit of no extra JS.

Or use Bootstrap for eye candy. Has been there for years and looks good enough.

In any case, it feels like we have come full circle, Red Queen race-style. Yay web development!

Re: DaisyUI: Tailwind CSS Components

#17

Post by Liquidor »

I don't really use Tailwind. I enjoy my (S)CSS.

I took a look at https://daisyui.com/components/button/ and immediately I see classes that look similar to Bootstrap.

So my question is: Why build components on top of something like Tailwind instead of just regular CSS? Or are you able to customize and use Tailwind mixed in with the components? Then sure why not I guess.

Otherwise it feels like going full circle here.

Re: DaisyUI: Tailwind CSS Components

#18

Post by fbn79 »

Liquidor wrote: post #17

I don't really use Tailwind. I enjoy my (S)CSS. I took a look at https://daisyui.com/components/button/ and immediately I see classes that look similar to Bootstrap. So my question is: Why build components on top of something like Tailwind instead of just regular CSS? Or are you able to customize and use Tailwind mixed in with the components? Then sure why not I guess. Otherwise it feels like going full circle here.

“Do not remove a fence until you know why it was put up.”

Re: DaisyUI: Tailwind CSS Components

#19

Post by bricej13 »

savanaly wrote: post #11
jug wrote: post #5

Doesn't this miss the point with Tailwind and why we have Tailwind in the first place?

>Doesn't this miss the point with Tailwind and why we have Tailwind in the first place? Not for me. Say I have a new app and I want it to have a left nav. I could write my own styles with tailwind or...I could just put a .menu on there and gets all the sensible defaults for padding, spacing, font size, background colors, etc. But having done that, I'll still want to edit the specific padding, spacing, fonts, and back…

I think it's the best of both worlds. Tons of free components right out of the box for non-designer developers (like bootstrap), but you still have the power of Tailwind at your fingertips.

I think the theming & semantic color support is underrated. You just use `-primary` or `-secondary` classes everywhere instead of hardcoding the colors. The theme colors are then just updated with css variables.

Dark mode is free, you don't have to pepper your code with a million "dark:*" classes.

Re: DaisyUI: Tailwind CSS Components

#20

Post by dmlittle »

coneonthefloor wrote: post #3

Tailwind has the Bootstrap problem, in that I can tell straight away that a website uses Tailwind, and for some reason that is off putting.

It depends on how much effort you put into it vs. just using any of the base templates/components that Tailwind Plus (previously Tailwind UI) has to offer.

If you look at their Showcase section[1], you can't tell it's using TailwindCSS for most of them (imo).

[1] https://tailwindcss.com/showcase

Post reply on HN