• AnarchoYeasty@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Ok so use modern frameworks and tools that implement the tailwind plugin. Because if you are shipping the entire tailwind css that’s a developer problem not tailwinds. News flash: using a technology wrong doesn’t make the tech wrong.

    • luciole (he/him)@beehaw.org
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      News flash: your snark makes you an unpleasant person. Read my comment again. I said tree shaking fixes this… unless you don’t know what content you’ll display and what classes you’ll need at build time. Not all sites are static.

      • AnarchoYeasty@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Unless you are going to be allowing custom html to be added the tooling is smart enough to figure out what possible classes your code can use. You’d have to do something dumb to not have the tools able to tell what components you are serving.

        • luciole (he/him)@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          More generally, the more you have a flexible editor in the app, the worst it gets. This is the use case where I ran into trouble.