3 ms·

You might argue that popularity is an indication of how many people are stuck with it due to (for example) Bootstrap’s unmaintainable nature. I agree with thre

You might argue that popularity is an indication of how many people are stuck with it due to (for example) Bootstrap’s unmaintainable nature. I agree with thread OP that tailwind is a mistake, but I’ve also never tried it myself, and I see a lot of people like it. I’ve avoided it because I have a rule of thumb to avoid any DSL embedded within another DSL. It’s a nightmare for static analysis, as demonstrated by the fact it needs its own compiler. That’s enough reason for me to stay away from it; I’ve got enough layers of compilation to worry about as it is.

nobleach 4y ago
I did use Tailwind. I read the book as well, just to really be sure I wasn't missing something. I hear the cries of "Tailwind fixed so much of my hatred for CSS" all over Reddit/HN/Twitter/etc and I really don't get it. At this point, I really chalk it up to "people want to be in the in-crowd". I'm sorry for those who really are experiencing a better quality of life. For me, I remember Bootstrap and how insane it was to remember all these utility class name (some with numbers to represent values that one might add to a CSS rule) But I get that people DO seem to love it... for whatever reason. I am just against adding it to a project as "the default". I get that it's just "one line to remove it" but it reminds me of the days when projects just included Lodash, jQuery and Bootstrap because... "everyone's using them anyway".