[ookblah]

lol what? i feel like you're jumping to the wrong conclusions here. i'm sure there is a subset of users that thought tailwind was "easier", but before tailwind there were a ton of other CSS frameworks like bootstrap, bulma, etc. that purported to make CSS easier and those never took off like tailwind did among devs.

people use tailwind because it's better to stand up something and maintain it when you're doing component based stuff without having to think of clever names on the fly or figure out what class does what and how did it fit into the hierarchy you created months ago. plus you get all the magic that you can't get with inline CSS. "Raw" css is in fact the easiest thing you can use, just style tags and have at it. Tailwind without that knowledge is nothing.

[aatd86]

I hope we can have something better than tailwind because having to preprocess/add a build step is very meh. That locks people into the js ecosystem.

Also, CSS should ideally be enough if it's simply about destructuring classes and composing them.