Thoughts on Tailwind CSS? Is it worth learning it?

Thoughts on Tailwind CSS? Is it worth learning it?

Beware Cat Shirt $21.68

Rise, Grind, Banana Find Shirt $21.68

Beware Cat Shirt $21.68

  1. 1 month ago
    Anonymous

    its good resume fodder but not widely adopted. theres no 'clear winner' for css frameworks so just pick up whatever resonates with you, or write raw css, it doesn't really matter

    • 1 month ago
      Anonymous

      >CSS frameworks
      I'm so fricking glad I didn't end up going into webshitting. Dodged a colossal bullet there.

      • 1 month ago
        Anonymous

        what is this supposed to contribute to the conversation?

        • 1 month ago
          Anonymous

          Hopefully it will serve as a warning to other anons considering a career in web development.

          • 1 month ago
            Anonymous

            I get paid 200k/yr to change button from blue to lighter blue

          • 1 month ago
            Anonymous

            Sounds reasonable.
            You'd have to pay me that much to touch a modern webshit codebase.

          • 1 month ago
            Anonymous

            That's how employment works.

          • 1 month ago
            Anonymous

            damn, they could be paying the some guy 20k in Bangalore. it's not 2015 anymore bub

          • 1 month ago
            Anonymous

            lol, ux and design is actually the one area pajeets can't into in the slightest

      • 1 month ago
        Anonymous

        As moronic as I feel running a compiler for my css, it is legit easier to use and faster anon. All my personal projects are using htmx and tailwind css now

        • 1 month ago
          Anonymous

          Don't feel bad, frameworks like Tailwind and Bootstrap, while breaking the idea of separating content from style, make maintaining projects much easier, and they also dramatically speed up front-end development processes. I say this as someone who has written probably close to 750k lines of CSS in their life.

  2. 1 month ago
    Anonymous

    No, Tailwind is a mistake.

    • 1 month ago
      Anonymous

      Everyone seems to be using it.

      • 1 month ago
        Anonymous

        >le ad populum argument
        Kys.

        • 1 month ago
          Anonymous

          nta but you didn't even provide reasoning as to why tailwind is bad
          you're the one that should kys, at least he has an argument

  3. 1 month ago
    Anonymous

    in a way, horrible.
    markup is now full of css classes, with no re-usability apart from tailwind classes.

  4. 1 month ago
    Anonymous

    how is this any different than bootstrap classes that have been around forever

    • 1 month ago
      Anonymous

      Tailwind classes are more atomic

      • 1 month ago
        Anonymous

        So why not write (S)CSS?

        • 1 month ago
          Anonymous

          You can still use a pre-processor with tailwind.

          • 1 month ago
            Anonymous

            You have missed the point.

          • 1 month ago
            Anonymous

            What is your point then? You did a terrible job of explaining yourself.

          • 1 month ago
            Anonymous

            If you want to write CSS, you should write CSS, probably with SCSS because vanilla CSS is pretty bad.

            If you want it all in your DOM, then use style=, that's what it's for.

            Tailwind is pointless, and you are cavern-brained.

    • 1 month ago
      Anonymous

      Bootstrap is more restrictive and less flexible, it aims to provide styling for the majority of component types as part of its framework. That means when you use bootstrap you don't make your own cards or carousel styles, you use the ones provided by bootstrap:
      https://getbootstrap.com/docs/5.0/customize/components/

      Tailwind doesn't provide components, it's a minimal and flexible framework that you build custom components and pages with. That means when you use Tailwind, for example, you make your own carousel and cards, but you do it with a standardized rule set (either the one provided as base or your own easily customized one).

      If you want to write CSS, you should write CSS, probably with SCSS because vanilla CSS is pretty bad.

      If you want it all in your DOM, then use style=, that's what it's for.

      Tailwind is pointless, and you are cavern-brained.

      You have never worked in a team on a large project.

      • 1 month ago
        Anonymous

        >You have never worked in a team on a large project.
        I am doing both at this very second.

      • 1 month ago
        Anonymous

        >That means when you use bootstrap you don't make your own cards or carousel styles, you use the ones provided by bootstrap

        !important;

  5. 1 month ago
    Anonymous

    just write what you need instead of bloating your webpage with a hundred different frameworks and other bullshit

  6. 1 month ago
    Anonymous

    its shit

  7. 1 month ago
    Anonymous

    Poor code reusability. Other than that, it's pretty much the only viable alternative to Boomerstrap.

  8. 1 month ago
    Anonymous

    I don't see the point of learning it. You still need to know css well enough to make use of it, but if you know CSS already, why would you even need this? It won't save you time.

    • 1 month ago
      Anonymous

      I concur. I'm not a front-end programmer but what I see from the sidelines implies that tailwind is just a "fancy" way of doing things that you can just as well do with just CSS.

      We once had an intern that whined about not having Tailwind CSS on the server and wanted me to install it. I declined his hipster request and told him to learn normal CSS first.
      Kicked him out soon after because he was useless.

  9. 1 month ago
    Anonymous

    it's the best way to do CSS

  10. 1 month ago
    Anonymous

    I don’t hate tailwind. It’s like ui libs and the like. You build on it a bit then next thing you’re writing stuff to compensate for other stuff to the point plain CSS would have been better. I say use sparingly and know when to quit and go to plain CSS.

  11. 1 month ago
    Anonymous

    >dude, it is css, be we renamed everything so midwits can feel smart when using it and others don't get it

    cmv

  12. 1 month ago
    Anonymous

    why should we memorise a bunch of bullshit?

    • 1 month ago
      Anonymous

      the main reasons are:
      - it's faster to write as long as your classes are not complex and don't require special transformations and so on
      - it has a built-in design system (because of the constraints)
      - no need to find the right .CSS files and look for the classes (this is a non-issue with modern tools though)

      also there's not much to memorize, since the classes are pretty much named after the real CSS properties

  13. 1 month ago
    Anonymous

    tailwindui beats bootstrap for app UI/UX imo, makes banging out nice looking MVPs a lot easier and faster for non-artsy devs.
    at the end of the day all CSS frameworks suck and you'll always feel like you're a monkey being told to "move it slightly to the lefft" by a bunch of morons with moronic opinions.

  14. 1 month ago
    Anonymous

    You're trading having a slightly smaller CSS file for shitting up your entire DOM with thousands of classes.

  15. 1 month ago
    Anonymous

    It's inline CSS with extra steps

    • 1 month ago
      Anonymous

      It's inline css with less steps actually. Tailwind is designed to be used with component-based frameworks like next or another react derivative, providing the style rules inline with JSX makes complex UI way easier to maintain.

  16. 1 month ago
    Anonymous

    frick no
    just learn real CSS you fricking tard
    i enjoy webdev but why is the default webdev a fricking stupid indian who cant do anything on their own?
    > SIR I NEED LIBRARY FOR THAT!!! HOW AM I SUPPOSED TO DO THAT WITHOUT A LIBRARY?? WHATS THE FRAMEWORK FOR THIS SIR?? PLS SIR HOW I CAN DO THIS WITH REACT SIR

    • 1 month ago
      Anonymous

      Everyone knows "real css". It's like the most basic shit imaginable to have figured out grids and flex containers, everyone learns this shit at the beginning.
      You're the only moron here. These frameworks exist so that a project has standardized styling across its components and pages, so Rajesh the stupid indian (ie. you) doesn't decide to be special and frick up maintainability. Inline style classes are also just a better way to develop front-ends, it keeps components and pages self-contained in a single file instead of having rules split across 10-20 different ones.

      >You have never worked in a team on a large project.
      I am doing both at this very second.

      Strong doubt. Any experienced front-end developer knows the benefit of using frameworks. I can't imagine what maintaining your god awful project is going to be like.

      • 1 month ago
        Anonymous

        >it keeps components and pages self-contained in a single file instead of having rules split across 10-20 different ones.
        this. like boostrap, it's much easier to maintain an html with some utility classes than having to update the css selectors+rules everytime someone decides to change the identifying class of any given html element

        unless you enjoy digging through hundreds of codeslop just because

      • 1 month ago
        Anonymous

        >Strong doubt. Any experienced front-end developer knows the benefit of using frameworks. I can't imagine what maintaining your god awful project is going to be like.
        Yeah which is why I use material-ui or bootstrap when I'm prototyping shit, so the users aren't looking at unstyled HTML during the initial rounds of testing.

        If you don't write your own CSS, you're not working with designers, and thus your opinion is worth less than trash on the matter.

        • 1 month ago
          Anonymous

          >If you don't write your own CSS, you're not working with designers, and thus your opinion is worth less than trash on the matter.
          you can't be real

          • 1 month ago
            Anonymous

            He's right though

          • 1 month ago
            Anonymous

            He's in the cave of unemployment that Plato talked about. You're not gonna prove to him how moronic he is, he must realise for himself.

            Maybe when he gets a job.

          • 1 month ago
            Anonymous

            >You're not gonna prove to him how moronic he is, he must realise for himself
            I tried

          • 1 month ago
            Anonymous

            It's appreciated.

          • 1 month ago
            Anonymous

            This thread is like watching two armies fighting for the top of mount Dunning-Kruger

          • 1 month ago
            Anonymous

            As if either of you have any idea what's being talked about or going on.

          • 1 month ago
            Anonymous

            Exactly

          • 1 month ago
            Anonymous

            Which side are you on?

          • 1 month ago
            Anonymous

            Nothing he said he is right. In the first place Tailwind is a framework meant to be used to create custom component and page styles but provide an underlying set of rules that use a standard. For instance if you declare p-1 (padding level 1) it's the same padding size anywhere, m-1 same thing, border-1 same thing. This ensures the rulesets are standardized. You can define the sizes yourself (I have a configuration for silver and golden ratios as an example) or use the ones provided as base by Tailwind.

          • 1 month ago
            Anonymous

            Yeah, you do the same with SCSS you homosexual inbred.

          • 1 month ago
            Anonymous

            And you can use Tailwind with SCSS if you want. You've misunderstood the point completely and have made blatantly false claims several times, stop posting, you're just embarrassing yourself at this point.

          • 1 month ago
            Anonymous

            So you have the same amount of CSS, less flexibility, a requirement for postcss to remove shit you're not using, AND you're bloating your DOM with a shitload of granular classes, for absolutely no benefit?

            It's time for you to go back to Kolkata.

          • 1 month ago
            Anonymous

            >less flexibility
            You act like tailwind can't be extended with classes, all it does is provide a basis for creating standard rulesets across a project. Why would you duplicate that effort when you're likely going to do the exact same thing if you're smart.
            >you're bloating your DOM with a shitload of granular classes, for absolutely no benefit?
            Yet again missing the point entirely, splitting your rules across 10-20 different files instead of just having everything encapsulated in the component JSX is fricking moronic. It makes the project less maintainable and slows down the development process. You're clearly some amateur who's never worked a real job.

          • 1 month ago
            Anonymous

            >splitting your rules across 10-20 different files instead of just having everything encapsulated in the component JSX is fricking moronic
            Ah yes, because I am perfectly capable of naming even a single project that I've worked on with less than 20 different components.

            Get back to watching your youtube tutorials.

          • 1 month ago
            Anonymous

            >20 different components
            Holy shit you don't even understand what I'm saying. You have 20 different components each with individual rulesets split across multiple scss files, worse, you're likely duplicating a shit load of styling across those files instead of just re-using it. Imagine if each component was ONE FILE. That's the point moron, it's way more maintainable and there's way less duplication of effort. I've never met someone as braindead as you before.

          • 1 month ago
            Anonymous

            >you're likely duplicating a shit load of styling across those files instead of just re-using it.
            You are a Black person if you don't see how tailwind is exactly that. In fact, you must see that's the case, because you're projecting that on my projects.

            Post your fricking github, trash.

          • 1 month ago
            Anonymous

            >tailwind is exactly that
            No it's not, it's literally exactly what you're doing but keeping everything encapsulated in a single file to make maintenance easier and to expedite the development process. Or what, do you mix component styling and rules? Do you have any idea how fricking stupid that is? Your project is going to turn into an inevitable mess to maintain if you do stupid shit like that.
            >post your github
            No homosexual who doesn't even have the decency to provide their own identity first is going to get my github.

            Next time, instead of being a moron who makes several false claims just ask people to explain something you don't understand to you.

          • 1 month ago
            Anonymous

            >asking people to be reasonable on IQfy

          • 1 month ago
            Anonymous

            >ask people to explain something you don't understand
            Alright well clearly I'm misunderstanding something then.
            >it's literally exactly what you're doing but keeping everything encapsulated in a single file
            Show me a component that uses tailwind that isn't littered with a bunch of class names.

          • 1 month ago
            Anonymous

            >isn't littered with a bunch of class names.
            No because that's the whole point of tailwind. You style inline so you don't have to maintain separate files dude, it's faster, easier and makes working on complex UI way easier. You also don't have to sort through a bunch of rules based off a container id or class that only work when that class is provided. That means you can easily rip out any part of a component and implement it into another one without having to copy the ruleset multiple times, thus creating a shitload of duplicate styles and slowing down page loading.

          • 1 month ago
            Anonymous

            >You style inline so you don't have to maintain separate files
            So you ARE moronic! Nice to know. That's not the reason inline styles are desirable.

          • 1 month ago
            Anonymous

            >that's not the reason inline styles are desirable
            >but I'm not going to elaborate or explain why
            Okay, you had a chance to ask more questions, like why your way of styling hits performance, but if you want to continue being aggressively moronic, that's up to you.

          • 1 month ago
            Anonymous

            >>but I'm not going to elaborate or explain why
            See my earlier post.

            He's in the cave of unemployment that Plato talked about. You're not gonna prove to him how moronic he is, he must realise for himself.

            Maybe when he gets a job.

          • 1 month ago
            Anonymous

            Ah yes, I, who leverage de facto frameworks used in countless projects in the professional world of front-end web dev, am the unemployed one, not the autist arguing against them. Not the autist who made it very clear from their false representation of the job of a UX/UI designer they have no idea what they're talking about.

          • 1 month ago
            Anonymous

            nta but that's one of the most attractive parts of inline styling and you sound deranged for disagreeing

          • 1 month ago
            Anonymous

            He's not deranged just autistically defensive because he thinks DOMs having a bunch of classes is le bad for [unintelligible reasoning].

          • 1 month ago
            Anonymous

            Using inline classes to style is just better. Oldgays always say you should separate content structure from style but in practice it doesn't make sense from the developer standpoint and doesn't do anything to impact the user experience. There's no benefit to doing so, you just make shit harder to maintain, take longer to develop and end up sacrificing performance _and_ footprint. That's why everyone uses these frameworks now. They work really well. The only place they don't make sense is on very small projects with maybe one or two components.

          • 1 month ago
            Anonymous

            Braindead neet

        • 1 month ago
          Anonymous

          You clearly have no idea what Tailwind is or how it's used.
          >If you don't write your own CSS, you're not working with designers, and thus your opinion is worth less than trash on the matter.
          You've never worked with a designer. I am a UI/UX designer and if I saw you working outside of the standards I set for the project, with the frameworks I proposed for the design, I'd have you sent for performance review and be reprimanded in the same day.

  17. 1 month ago
    Anonymous

    It's great.
    Lowest bundle size and highest performance even compared to vanilla CSS.
    Fastest way to write CSS for component based web applications.
    Can be combined with headless component libraries to properly separate styling from functionality.

  18. 1 month ago
    Anonymous

    >named classes BAD
    >just use multi-cursor editing lmao

  19. 1 month ago
    Anonymous

    Tailwind is rather large (3654 kb uncompressed) compared to, lets say, Bootstrap (ca. 500 kb uncompressed). However, if you build your app with Vite.js it will cut off all the fat. I'd say that, as always, it depends on what you want to make. If it's a static onepage with minimum functionality just pick whatever you feel comfortable with.

    • 1 month ago
      Anonymous

      >500kb uncompressed
      What the frick are you on bootstrap is several megabytes larger than Tailwind uncompressed.

      >That means when you use bootstrap you don't make your own cards or carousel styles, you use the ones provided by bootstrap

      !important;

      Ajay I need to see you in my office immediately.

      • 1 month ago
        Anonymous

        >What the frick are you on bootstrap is several megabytes larger than Tailwind uncompressed.

        If you use it's Javascript. I thought this is about SCSS/CSS?

        • 1 month ago
          Anonymous

          Literally just the css and scss maps are 6.1MB

          • 1 month ago
            Anonymous

            bootstrap.css ... 280,813 bytes

          • 1 month ago
            Anonymous

            Are you forgetting the rest of the framework? Utilities, grid, reboot, rtl variant, etc? You don't even have the map for that file included too. JFC.

          • 1 month ago
            Anonymous

            >Utilities, grid, reboot, rtl variant, etc?
            All included

          • 1 month ago
            Anonymous

            Bullshit.

          • 1 month ago
            Anonymous

            Nevermind. Anon, you were born to be a frontend dev.

          • 1 month ago
            Anonymous

            >lies
            >gets blown out
            >comes up with some bullshit to save face
            Just have a nice day, you were born to be a nocoder if you can't even figure out you gave the byte size for just the base bootstrap css.

        • 1 month ago
          Anonymous

          Even the minified css is still 2.1MB btw. Tailwind is a much lighter framework, I have no idea where you got 500kb from.

  20. 1 month ago
    Anonymous

    Webshit will be the first thing to get automated with LLMs. Good riddance

  21. 1 month ago
    Anonymous

    Write semantic markup and use a classless style sheet.

  22. 1 month ago
    Anonymous

    >Thoughts on Tailwind CSS?
    good and time saver
    > Is it worth learning it?
    yes 100%

  23. 1 month ago
    Anonymous

    Tailwind helped me understand CSS a lot better. The documentation is excellent and whenever I wanted to do something I could almost always find with a Google search or Ctrl + f on the Tailwind website and I found what I was looking for.

    Mix it with Shadcn for some solid components and you have a solid foundation.

    • 1 month ago
      Anonymous

      Tailwind is genuinely fantastic, frameworks like this will move us out of the every-website-looks-like-bootstrap era. It gives devs and designers way more control over UX too so it'll lead to more intuitive UI as well.

    • 1 month ago
      Anonymous

      Also, not to harp, but you should really just build your own components, most of them are quite simple and take very little time to create when you use a react framework. Right now most of my new projects are being handled with Next & Tailwind, with Strapi as a back-end. For electron I use pretty much the same thing, Nextron with Tailwind and Strapi for the local back-end. It's really nice, everything from the web application front-end is basically a drop-in for the electron application. Plus, if the electron app needs to have its own capabilities, the tech is still the same, so there's a unified standard across everything.

Comments are closed.