|
|
|
|
|
by k1w1
1178 days ago
|
|
The problem with Tailwind is that it is write-once code. You don't get any leverage. Ideally as you write more code you get more reuse and writing future code becomes faster. In theory CSS classes act like this too. As you have more (well designed) CSS classes then writing future CSS becomes easier because you can reuse the past work. Tailwind breaks this benefit that by encouraging you to write your CSS with glorified styles. |
|
And code that uses Tailwind is reusable as long as you use components (React, Vue, Svelte, WebComponents, CSS components with @apply, it doesn't matter). Those are reusable.
Trying to use Tailwind without components, in a CSS-garden style page for example, is just trying to fit a square peg in a round hole. It's just the wrong tool for it.