5 ms·
The first one is a find and replace nightmare on any sufficiently large project and akin to inline styling. The second negates the point of utility classes.
by hisnameisjimmy 7y ago
The first one is a find and replace nightmare on any sufficiently large project and akin to inline styling. The second negates the point of utility classes.
- antonkm 7y agoNo, it does not. They're not exclusive. I've written large pages that pretty much only used component classes for pills and buttons, with Tailwind using @apply. All the other elements used utilities. Paired with purge-css you get small CSS bundles and really quick styling. You'd often use something like a component based JS framework or a server rendered templating language, making it easy to contain all utilities with shared logic in one place.