>>106696138
>who uses this?
reddit

I prefer it to the agony of traversing your own css classes and structures

CSS preprocessors are for front-endlets.

>>106696138
Think of it as a moderately better alternative to inline style tags.
As for why you would want inline styling, it makes a lot of sense if you use a reusable component system like React. The traditional advice might to separate markup, style, and behaviour but in practice that just means you have to add three files instead of one while also having to name a bunch more stuff.

If you instead decide to go for small widely-reused components in one .tsx file with tailwind styles, you may find it lets you work faster while also keeping things easier to maintain. You might even find that you can actually share components between projects.

>>106696138
it's just inline css with extra steps. and that's a good thing.
t. full stack web shitter

>>106696235
this

>>106696235

Pretty much. There is already so much class bloat in modern front end. Being able to outsource the css to one thing and just call it as you need it takes away 30% of the pain.

>>106696235
Yeah, the whole advice about not using inline falls apart with components.

Still waiting on pico.css except made with tailwind.
I guess I'll have to one day vibeslop it myself, cuz everyone else is a lazy fuck.

I've used it. It's okay. My single gripe with it is that it makes the HTML look ugly and because I'm autistic like that, I mostly avoid using it outside of work.

>>106696138
>just put "pxcvb25-ttrtj59-ax" in the class name and you'll get a half-baked template
So it's just like bootstrap?

>>106697754
>pico.css
>82 KiB minified
That is not pico.

>except made with tailwind
You mean auto purging unused classes? You can use PurgeCSS for that.