3 ms·
For anyone reading this since its pretty high, it's one of those cases of really high HN bias, that actually got to me. I'm not blaming OP, the question seems
by Trufa 2y ago
For anyone reading this since its pretty high, it's one of those cases of really high HN bias, that actually got to me.
I'm not blaming OP, the question seems innocent enough, but I had this bias and some others myself until I used Tailwind for an actual project and have never looked back, and most of the criticism that appears in HN is just misunderstood concepts and harsh sounding soundbites.
I distrust HN's general sentiment on stuff more (if there is such a thing but you know what I mean), I check for myself.
Regarding tailwind specifically, it's the modern way of "just css" which goes amazingly well with having the component abstraction level.
You don't abstract your css, you keep it all in base level, you abstract components, in this particular case you would go to your button component and change all of the application's button at once.
- 101008 2y agoThanks for explaining, that makes sense. And yes, my question was innocent. I am not a frontend dev, I used to do some CSS and vanilla JS back in the day. Thanks for taking the time to explain it to me!
- pupppet 2y agoCreating a component out of everything always sounds good in theory but falls apart in practice. There's always that oddball element that doesn't quite work as a component, and then you end up with a component and a bunch of the outliers that you need to remember to manually update.