ChipTuner on Nostr: I've used a few. Lately I really like dasiyUI for rapid development. It reminds me of ...

I've used a few. Lately I really like dasiyUI for rapid development. It reminds me of a classic somewhat opinionated style-sheet similar to the old bootstrap stuff (at least when I first played with it). I used TurretCSS and a few other opinionated kits before switching to tailwind. Flowbite and a few others implement their styling in their component libraries. It looks good, but it's not as easy to change things globally, like changing the style of inputs, you'd have to go to every input and modify the classes (or hack some css to override them). For migrating existing codebases I think daisy is awesome, it just kind of works, and is very unified, especially themes and coloring. When using tailwind, I would always create classes for colors for a more unified theme and easy to remember. Like `input-primary` or `text-primary` or `text-primary-background` stuff like that. So I'm not even using the classes that flowbite and others use in their components.

Point being, learning frontend from scratch, I lean toward large single style-sheets, and whatever framework gets me there. I've tried both over the past few years and realized I just tended toward consistency with less time investment which brings me back to big single style-sheets (I use scss so it's more like a dozen named style-sheets instead). Daisy UI is pretty close to that for me, and themes, and pretty easy adjustment to those themes.