DaisyUI – Tailwind CSS Components

Re:DaisyUI – Tailwind CSS Components by onion2k on Friday July 30, 2021 @03:01AM (#28005219)

Back when Bootstrap 2 was the most popular UI library one of the biggest problems with it was that the defaults were good enough that no one changed them, and consequently every SaaS startup's product looked the same for about 5 years. Pushing people to tweak things while still giving them a solid foundation is a good thing.

I'm not saying that's necessarily the case here, but there is a strong argument in favor of not making the default theme for a UI library look perfect.

[ Parent | on HN ]

Re:DaisyUI – Tailwind CSS Components by jhgb on Friday July 30, 2021 @07:01AM (#28006657)

> the defaults were good enough that no one changed them, and consequently every SaaS startup's product looked the same for about 5 years

Sounds like native GUI experience on Mac or Windows for quite some time, then? I'm certainly not offended when all buttons look the same. At least I immediately know that they're buttons.

[ Parent | on HN ]

Re:DaisyUI – Tailwind CSS Components by mosburger on Friday July 30, 2021 @09:20AM (#28007641)

I still think about the quote I once heard around that era... "Made with Bootstrap" is the "ft. Pitbull" of web design.

[ Parent | on HN ]

Re:DaisyUI – Tailwind CSS Components by hashedout on Friday July 30, 2021 @03:56AM (#28005582)

This argument makes perfect sense. The easy adoption that never gets updated in future sounds bland.

[ Parent | on HN ]

Re:DaisyUI – Tailwind CSS Components by breakfastduck on Friday July 30, 2021 @12:18PM (#28009574)

I take it you dislike native software then...

[ Parent | on HN ]

Re:DaisyUI – Tailwind CSS Components by onion2k on Friday July 30, 2021 @12:24PM (#28009628)

I'd do 100% of my job in a browser if I had the option.

[ Parent | on HN ]