Don't use Tailwind for your Design System

Re:Don't use Tailwind for your Design System by balfirevic on Wednesday January 11, 2023 @07:20AM (#34337601)

  > const headerClasses = [(list of Tailwind classes here)];
  > <header className={...headerClasses}>...</header>

Why wouldn't they extract the header as a higher-order component? That would make more sense even without Tailwind, and I haven't heard anyone in the Tailwind community advocate against that.

[ Parent | on HN ]

Re:Don't use Tailwind for your Design System by have_faith on Wednesday January 11, 2023 @07:27AM (#34337640)

I think this is just an example but `header` is a standard HTML element. It's not always necassary to seperate every single element into it's own component. Every time you make a framework component you add overhead to the rendering of the app.

[ Parent | on HN ]

Re:Don't use Tailwind for your Design System by balfirevic on Wednesday January 11, 2023 @07:39AM (#34337717)

* * *

[ Parent | on HN ]

Re:Don't use Tailwind for your Design System by replygirl on Wednesday January 11, 2023 @07:36AM (#34337697)

> Every time you make a framework component you add overhead to the rendering of the app.

not true, separating components by concern can save you a lot of fiddling with memoization

[ Parent | on HN ]