4 ms·
I have _serious_ doubts about the longevity of tailwind. It adds unnecessary tooling to recreate inline styles with theme support. I tried adding it to a projec
by neurotrace 5y ago
I have _serious_ doubts about the longevity of tailwind. It adds unnecessary tooling to recreate inline styles with theme support. I tried adding it to a project which used other technologies listed here and it was obnoxious to use. You end up with class name soup unless you combine all of the styles under a combined class. Once you do that, it's literally just normal CSS with extra steps
- adrianthedev 5y ago> Once you do that, it's literally just normal CSS with extra steps. Yeah, I agree. That's not the way to go. Components is the way to go. Regarding using tailwind in general, I had a few issues in the beginning, too, until I figured out how it's supposed to be used. It is a bit tough to use it with frameworks that don't allow you to create components in a more modular way. But if you get to create these components, it's really a joy. It reminds me a bit of the BEM methodology (just a bit). Again... it's also a matter of what each person is vibing with.
- neurotrace 5y agoComponents don't stop the soup though. It's a fundamental issue where you're just replacing inline styles with classes. But hey, you do you