Re:Master Styles – The First Virtual CSS Engine
by inopinatus on Thursday March 24, 2022 @07:19PM
(#30796739)
I didn't expect to love utility-first CSS, but I'm a Tailwind convert after using it in production apps. It's a great productivity boost, and a terrific fit for server-rendered partials and their descendants.
This client-side production of styles on page load, however, is a step too far, since it's inevitably brittle to JS issues and FOUC.
Re:Master Styles – The First Virtual CSS Engine
by iruoy on Friday March 25, 2022 @05:13AM
(#30800009)
This is what I thought at first too. But this runs in javascript for some reason.
I see no reason for such a thing and the website doesn't explain why either. If you go to the Why page they're only boasting about their syntax.
Re:Master Styles – The First Virtual CSS Engine
by iruoy on Friday March 25, 2022 @05:16AM
(#30800029)
Essentially they're moving the compile step of Tailwind to the browser. On each page load. For no benefit.
Re:Master Styles – The First Virtual CSS Engine
by danielvaughn on Thursday March 24, 2022 @07:38PM
(#30796921)
Exactly right - Tailwind's constraints are what differentiate it from just inline styling. I've only glanced at this landing page but from what I see, I don't understand the value proposition.
I think cleaning up the hyperbolic marketing language would go a long way for me in terms of taking it seriously (the entire "Why" section does not actually communicate any real information).