• kambusha@sh.itjust.works
    link
    fedilink
    arrow-up
    30
    arrow-down
    1
    ·
    12 hours ago

    I was very much against frameworks initially: tailwind, bootstrap etc. However, when I started really building sites & apps using components, I found tailwind made my life a lot easier, so I could easily see and change styling while writing code/html, and it would only affect that component.

    Beforehand, I was trying to come up with names for CSS classes all the time, and then I’d change one thing, and fuck up styling on a diff page.

    • moriquende@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 hours ago

      Yep, a component is a good abstraction level, no point in making life difficult by creating and coming up with names for smaller parts.

    • Karjalan@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      10 hours ago

      Honestly love tailwind. Once you get used to all the names/abbreviations and how they work with sizes and states etc. it’s much easier to see what’s happening when eyeballing code.

      Makes reviewing and bug fixing easier too.

      I get that early on it feels annoying. I recall disliking it the first time I learnt it, but then when I went back to regular css and classes I really missed it.

      • moriquende@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 hours ago

        Any passable editor nowadays does the heavy lifting for you, you can usually even write the CSS tag you want and it’ll show you the options.

      • FooBarrington@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        Except that you learn the class names once and re-use them across all your projects, whereas CSS classes are different for every single project.