A Utility-First CSS Framework for Rapid UI Development(tailwindcss.com)

almost 5 years ago from Dima Braven, founder at itmeo.com

  • Chris GriffithChris Griffith, almost 5 years ago

    If you're working in any templating or component framework you should create a reusable component for something like a button. Then you only write the classes once in the component and then in something like React, call <Button> everywhere else. This also provides a source of truth.

    Try using it in a project before providing the "hard to decipher" argument. Sure, there are a lot of classes there, but you can see every style that is being applied – right in the markup. I'd argue that is easier than parsing through markup and stylesheets and dealing with inheritance issues.

    5 points
    • Olivier FOlivier F, almost 5 years ago

      OK, but if you're going to make a component, why not put normal CSS in that component? I use Vue which has single-file components and scoped CSS. With these capabilities I have a hard time seeing the advantage of tachyons and tailwind.

      2 points