Re:Twin – Tailwind with the flexibility of CSS-in-JS
by earthboundkid on Thursday December 03, 2020 @07:43AM
(#25288284)
Everyone hates Tailwind before they use it. None of your criticisms are new. Actually using Tailwind makes you realize that creating CSS classes for your components is basically a waste, since you only ever use them in the component itself.
- Unless the same class can be used in multiple HTML templates, there’s no point in giving the class a name.
- Only very general CSS can be used in multiple templates because anything specific will have the brittle base class problem.
PS mr-3 is .75rem and mr-4 is 1rem, so you can see with your eyeballs if you’re using the wrong one.
- Unless the same class can be used in multiple HTML templates, there’s no point in giving the class a name.
- Only very general CSS can be used in multiple templates because anything specific will have the brittle base class problem.
PS mr-3 is .75rem and mr-4 is 1rem, so you can see with your eyeballs if you’re using the wrong one.