3 ms·
As I commented on Mastodon: Today's "Tailwind-in-HTML" is tomorrow's tech debt on a scale we haven't seen since the AngularJS days from a decade ago. It won't
by jaredcwhite 3y ago
As I commented on Mastodon:
Today's "Tailwind-in-HTML" is tomorrow's tech debt on a scale we haven't seen since the AngularJS days from a decade ago.
It won't be pretty.
(But perhaps a future job opportunity for folks who can rebuild design systems using real CSS and web standards.)
- phero_cnstrcts 3y agoI don’t use it but what I think is cool about it is: if you use it with inline JavaScript you never have to think about separation of concerns ever again.
- chatmasta 3y agoBetween Tailwind and htmx, we can probably run Doom in HTML attributes.
- simonpacis 3y agoThe classes are in the HTML-document regardless of Tailwind. I should think it would be possible to create a tool that removes them from the HTML and generates whatever they did in a separate CSS-file, if you wanted to move on from Tailwind. Not pretty, but wouldn't be that bad, honestly. But I might just be naive.
- johnnypangs 3y agoI found a bunch of them, here’s one: https://github.com/Devzstudio/tailwind_to_css https://github.com/Devzstudio/tailwind_to_css