Post

Bonus points: css tagged template literals are parsed as css your editor's language server so you can actually use prettier, stylelint, or any other linter or formatter.

I mean it would. But I need to copy/paste the rules. And a lot of them are compound rules.

FWIW that's what I call a difference between "framework" and "library". The former requires your full, undying commitment. The latter you can use whatever parts you like, while ignoring the parts you don't.

If you want SSR with elements that can be rehydrated, yeah. Well, if you turn off the server side and output the HTML, it can be static, and perhaps bloated compared to just using a server template system. I think the main idea is that this format satisfies all possibilities.

I'm not sure why that wouldn't simply be the HTML rendered on the server?

Tailwind V5: "Do you remember OUR feature in V4? We are making them even better and we are reducing the JS for a faster build!" Tailwind V6: "No more JS! Now the CSS can run directly into the browser!" Tailwind V7 redirecting user to the MDN pages ...

And yet, if you wanna bet, Tailwind will still be primarily used with its "proprietary design system" and web components will never see mass adoption. 🔮

Not that I'm a die-hard Tailwind guy or anything, but their now using CSS variables doesn't really seem like something to care about if you're already buying into the Tailwind philosophy of just using the predefined classes instead of having to come up with new class names.