Honestly this is amazing. Tailwind has a convoluted build process and creates a massive mess of html classes. This was much simpler to install and looks to be pretty easy to use too. Already got VSCode tooling working too (versus the Tailwind plugin which is just as complicated and convoluted as Tailwind itself).
I feel like this is a conflation of two very different ways to use frameworks.
If you write semantic classes and use @apply in tailwind or variables in pollen, it boils down to pretty much the same thing.
If you use tailwind utility classes in html directly you'll have what you describe, but you can still run the cleanup scripts and be done with it.
The strength of either framework imho stems mostly from having a config and a subset of options, a design system, contrary to just writing vanilla css. But any mess of unused classes is always yours to keep or clean.
