3 ms·
I think the reason why tailwind is as popular as it is, is because it really ties in with the "change something, save, then immediately see the result" loop and
by sureglymop 2y ago
I think the reason why tailwind is as popular as it is, is because it really ties in with the "change something, save, then immediately see the result" loop and dx of modern day web development.
Yes, this works with regular css too but it's the fact that you can do bigger changes inline quickly without making up a class (and god forbid you already have a different class affecting the same element and it gets hairy). Personally I think this is nice, it's great to immediately see results and then adjust. But dx is not the only thing that matters and there are tradeoffs too. Personally I would use tailwind for personal projects but I don't think I would try to introduce it at work.
- bythreads 2y agoAnd thereby you kill all inheritance, that is the while point of css. I find it more magic to change a single class at root and have the entire design reflow (on purpose) - Its beautifull when combined with shadowdom and wc
- sureglymop 2y agoI think that's a good point that I've even struggled with in practice. What I would really want is to be able to write tailwind css classes but then have it automatically turned into regular css that makes sense on save. I really don't like coming up with class names and such.