Switch from UnoCSS to Tailwind 4?

Task type
Project
Changed

Context

I started using UnoCSS at Freelock. It handled some things that were tricky for us like fonts and icons. I have spent a ton of effort on tuning config and still have some issues.

Utility class challenges

Parsing tokens in code. I tried to remove utilities that were only used in @apply using {enforce: pre}. However it's been tricky to get right across my theme css, components, and modules.

Would tailwind help at all or does it face the same problem?

Utility class collision. Some classes exist in core/contrib themes - .block, .inline.
UnoCSS allows easy renaming, IE .d-block, .d-inline.