Well you should have included something for guys like me: “I have no idea what Tailwind or DaisyUI bring to the table, I just use them because the team decided on it before my time”.

Daisy is fine for simple stuff but their no-js stance makes some of the more advanced ui very clunky using checkbox tricks etc

I like daisyUI because it provides a set of components which are extensible with Tailwind. I have found it much easier to extend daisyUI’s components than I ever could when using e.g. Bootstrap. Conceptually, I think it definitely goes against the grain of what Tailwind stands for, but it gives me some sane options out-of-the-box, which I can then modify as needed.

Personally, I’m in no position to start composing my own class-soup components, so I like having daisyUI as a baseline. Plus, it has good theming support.

I don’t like that the new versions are so bleeding edge in terms of browser support, but that will work itself out over time. It is nice that I no longer need to use npm to install daisyUI, which greatly simplifies the dependency stack for my back-office applications.