Thanks for the link. The twin.macro is actually a compelling argument against my favoring of CSS-in-JS, because it "combines the best of both worlds," but for the same reason, it also increases complexity by adding yet another interlinked dependency downstream of Tailwind.
So, how's this: I promise I'll try the playground for 30 minutes sometime soon. :)
But I don't believe that's enough to learn it, because you'll still need to be constantly referencing the documentation to remember all the weird little utility classes. That's why I didn't like Bootstrap - it required memorizing some esoteric language that is totally useless ten years later. Whereas the CSS I learned in 2004 is still (mostly) just as useful today as it was then.
The reason I'm conservative in the technologies I adopt is because I've been doing web development for nearly 20 years now, and I've seen five or six cycles of fads begin and end. Very few technologies stand the test of time, and it sucks if you end up stuck with one of them on the tail end (heh) of its hype cycle. Or sometimes it's not even the end of the hype cycle, but just a major upgrade to a new version that requires you to change hundreds of files in your codebase (this is the main reason for my dislike of MUI). I don't know if Tailwind has that issue with upgrades, but I know CSS certainly does not.
I’m similar, webdev since the pre-jQuery days, and hate framework churn. Tailwind is kind of like jQuery in that it gives a consistency layer that CSS was missing (just like jQuery gave a better way to interact with the DOM).
Either way you find it, glad you’ll be giving it a shot!
I had the same feeling about bootstrap (and I also never really bought into it when I used it back in the day; I figured something better would come along)
Tailwind is not that. Tailwind might disappear over time, but only because future improvements to CSS might borrow ideas from Tailwind
So, how's this: I promise I'll try the playground for 30 minutes sometime soon. :)
But I don't believe that's enough to learn it, because you'll still need to be constantly referencing the documentation to remember all the weird little utility classes. That's why I didn't like Bootstrap - it required memorizing some esoteric language that is totally useless ten years later. Whereas the CSS I learned in 2004 is still (mostly) just as useful today as it was then.
The reason I'm conservative in the technologies I adopt is because I've been doing web development for nearly 20 years now, and I've seen five or six cycles of fads begin and end. Very few technologies stand the test of time, and it sucks if you end up stuck with one of them on the tail end (heh) of its hype cycle. Or sometimes it's not even the end of the hype cycle, but just a major upgrade to a new version that requires you to change hundreds of files in your codebase (this is the main reason for my dislike of MUI). I don't know if Tailwind has that issue with upgrades, but I know CSS certainly does not.