3 ms·
That is the point: which kind of projects? You all fight, but nobody says what exactly they develop. A webpage and Tailwind is absolutely fun. An app with reus
by progx 3y ago
That is the point: which kind of projects?
You all fight, but nobody says what exactly they develop. A webpage and Tailwind is absolutely fun. An app with reusable complex components, Tailwind is a pain. Themes, dynamic tailwind is a pain, static, tailwind is ok.
There are endless possibilities. The problem is, that some people think you can use Tailwind for everything and then they made simple things unnecessary complicated.
- whstl 3y agoI disagree 100% with that. I much prefer using Tailwind for complex apps with reusable components. Because then you don't have a lot of repetition, redundancy is as much as BEM. For static webpages (unless it is assembled by a static blog engine or something), I don't particularly enjoy it, because of the repetition. With components+Tailwind you have as much duplication as you'd have with pure BEM. All personal experience and opinion, of course.
- afiori 3y agoI like tailwind but I only ever used it in a JSX context, if I had to author plain html I would likely never choose it.
- openplatypus 3y agoNot my experience. We built a full rather complex and feature full application using Tailwind. How? Reusable components (we use Vue, but that’s just one option). I remember this being endorsed approached by Tailwind creator. No complaints.