Live data from Hacker News

DaisyUI – Tailwind CSS Components

daisyui.com

1–10 of 174 posts

Re: DaisyUI – Tailwind CSS Components

#5
I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions…

I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not superb like the actual TailwindUI library which is incredibly well thought from a visual design perspective. Those components are perhaps less shiny than these but they are incredibly functional and way more intentional.

This is a good effort though and I hope to see it improving.

Re: DaisyUI – Tailwind CSS Components

#6
This is a very nice step in making Tailwind more Bootstrap like (read beginner friendly). One common complaint about Tailwind is that it makes the HTML look very full (full of classes).

A very good example on OP's website for a button:

Using tailwind:

  Button

Using daisy:

  Button

Although I personally think that the corners at a bit too rounded by default, giving it a very amateur look but I think you can customize that.

But a very promising project indeed.

Re: DaisyUI – Tailwind CSS Components

#7

Anyone with experience using Tailwind UI want to comment on how this compares?

Here is my quick observation on a cursory glance.

DaisyUI is beautifully written. This can be the kit with a boatload of work done for you. Think like Bootstrap but better with Tailwind. You can use this to teach how to write well thought-out CSS codes, separation, and extensibility.

TailwindUI is more like Bourbon[1] (was my go-to Sass tool) but on the structural interfaces done for you. I'm standardizing out Web, WebApps, and marketing materials to start with TailwindUI. Someone with good chop of CSS/Tailwind won't likely need to use TailwinUI but it can be a fast tool for teams. It is highly extensible but also has the double-edge sword criteria that a rookie can just keep copy-pasting, repeating codes and still work (not a good thing).

Will we use DaisyUI for the team? Unlikely!

Will I use it for some quick but still larger project, marketing page? I might very likely.

1. https://www.bourbon.io

Re: DaisyUI – Tailwind CSS Components

#8

I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions… I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not…

Agreed. Not to sound too critical, but it looks off.

Re: DaisyUI – Tailwind CSS Components

#9

I’m not saying this is ugly but the visual execution of some of these components is poor. No good usage of padding in some examples, poor ratios between the typography and the containers, inconsistent use of different line widths and border radius, weird and incosistent design choices in spacing and proportions… I mean. This looks alright and it will certainly make any UI look pretty decent, but the execution is not…

I think it is not a fair comparison with the Tailwind UI where there's probably more than one person doing the work plus the whole expertise of the actual Tailwind authors in the mix.

If you are able to observe what is severely lacking in this implementation, I am pretty sure that the Github author would welcome your suggestions / comments / PRs and any contribution to make this better.

For a start, this is actually good (enough).

In the same vein that TailwindUI is still continuing to evolve as the maintainers are finding optimization to make it better.

Post reply on HN