6 ms·

Anyone interested in this approach may also like Tailwind https://tailwindcss.com/ https://tailwindcss.com/

• thestepafter 8y ago
  Tailwind is absolutely fantastic. I can code CSS 2-3 times faster and I no longer hate doing it.
  • evolve2k 8y ago
    How do we classify the progression that is tachyons/tailwind? Each time I see a new CSS framework I also think, is this yet another framework for devs that can’t desigh or is someone working to move the needle beyond what tachyons/tailwind have set a new place of maintainable CSS.
    • m45t3r 8y ago
      > How do we classify the progression that is tachyons/tailwind? Each time I see a new CSS framework I also think, is this yet another framework for devs that can’t desigh or is someone working to move the needle beyond what tachyons/tailwind have set a new place of maintainable CSS. AFAIK, functional CSS frameworks like Tailwind are getting relevance thanks to the recent boom of functional programming.
• subhajeet2107 8y ago
  How is this different from inline styling ? this throws class inheritance out of the window
  • theoctopus 8y ago
    The intention is that for repeated styles, components are extracted: https://tailwindcss.com/docs/extracting-components https://tailwindcss.com/docs/extracting-components
  • brunoc 8y ago
    A lot of modern CSS frameworks choose to ignore the cascade. This trend has grown in response to how difficult it is to avoid regressions at scale - large or multiple projects, lots of components, lots of independent teams, etc. The cascade really is an elegant and efficient idea but it becomes really difficult to manage as projects grow. The different with inline CSS is that those helpers are the building blocks — that’s where your standardize your design system metrics. As others have pointed out this library provides a mechanism to abstract into components as well.