News for hackers. Stuff that matters.

A comment on Why Tailwind CSS Won. Parent comment

Re:Why Tailwind CSS Won by deprecative on Wednesday August 16, 2023 @07:31AM (#37145474)
You're just using someone else's padding and margin classes. At least when you write your own it makes sense instead of Tailwind's alphabet soup bloat.
[ Parent | on HN ]
Re:Why Tailwind CSS Won by ajanuary on Wednesday August 16, 2023 @08:12AM (#37145833)
Not really. Tailwind lets you configure your own spacing and breakpoints. You get to pick what those numbers mean.
[ Parent | on HN ]
Re:Why Tailwind CSS Won by deprecative on Wednesday August 16, 2023 @05:45PM (#37154311)
That's just a CSS variable. You don't need Tailwind for that.
[ Parent | on HN ]
Re:Why Tailwind CSS Won by ajanuary on Thursday August 17, 2023 @05:57AM (#37159417)
Never said you did. I was just explaining that you aren't "using someone else's padding and margin classes".
[ Parent | on HN ]
Re:Why Tailwind CSS Won by cantSpellSober on Thursday August 17, 2023 @09:09AM (#37160995)
They are CJS modules or (ideally) Typescript. CSS custom properties (variables) are slightly different.

    import type { Config } from 'tailwindcss'
    
    export default {
      content: [],
      theme: {
        extend: {},
      },
      plugins: [],
    } satisfies Config
(not arguing for or against TW here)
[ Parent | on HN ]