All the cognitive load you save is immediately burdened by scanning 60-100 CSS classes in a 200-300 line length HTML element. And this repeated over and over and over in a ginormous number of lines. Giving you a massive migraine.

Turns out HTML size also increase by 7-20x in tailwind CSS.

Tailwind CSS is "write-only" code. Maintaining a site developed by someone else who has gone full-blown worship of the Tailwind Dao is a nightmare.

I guess Tailwind Dao masters are outmatched only by HTML Vice Police :)

Look, it's strictly pragmatic approach, i end up creating utility classes anyway and i'm really glad someone did this for me.

Maintaining Tailwind (or a mix of Tailwind and CSS) is routine, just like it should be.

And i'm talking about web app development, markup is cluttered anyway (tsx or whatnot), semantic effort is already put in components and such. So yeah, saving some cognitive load works and helps in case of Tailwind.