Why developers HATE TailwindCSS.

Trying to figure out why TailwindCSS provokes such a strong mix of love and hate among developers. Here are the main items that have made it the perfect choice for some, yet a source of controversy for others.

#TailwindCSS #WebDevelopment #CSS #CodingDebate

[Joooooooooooosh]

Tailwind makes me want to vomit. It's a trendy way of writing horrible sloppy UI that makes people feel better about not being able to grasp the concept of semantic styles. (And yes, I'm a developer, so your video is accurate.)

[roebienarnaiz]

As a newbie, I learned basic CSS then discovered TailwindCSS I used it and it further improve my knowledge in vanilla CSS.

[salmanhossain]

As a new Developer, I like Tailwind very much.

[aldanasjuan]

Hater here. I prefer pure css in svelte, either scoped or globally so the html looks clean. And I work hand in hand with designers so custom designs are easier with pure css/emmet.

[clown]

Actually, this is just one way to use it. If you don't like inline styling, you can @apply tailwind classes in your css file, so you can create your own classes. I will never understand people who hate on tailwind, and the only thing they can say is that it requires inline styling. Just take a look at the documentation before hating on something.

[HoratioKJV]

If Tailwind is truly straightforward and advantageous, why did its creators take years to develop Tailwindui and why is there a cost associated with the complete version?

[hamidrezakaramian]

I can't find anyone (in my co-workers) who hates Tailwind, we love Tailwind, tailwind changes the industry and it's so amazing.

[GuilhermeFArantesSouza]

Aren't you able to create your own classes as a mix of the tailwind classes? I thought that was the way to use it.

[diogen]

I am wondering how there are lots of paradigms of separating and isolating the code, that this is good, and at the same time people encourage applying tons of css classes for styling a single div. This mess with 3 lines of css classes in a single div could be useful only if it is not you who will maintain the code after somebody. Css should be isolated as well. However in some cases tailwind is very useful.

[jacobgoldenart]

I really want to like tailwind, but I find for the way I like to tweak my css in the browser, it's not that great of an experience. I usually create some html/css and then start adjusting the styles/css in devtools so that I can see my changes in the browser and adjust things at the pixel level and add and remove classes as needed, even with live reload, this is tricky to do with tailwind, cause you can't really 'tweak' tailwind classes in the browser because they are compiled, you can only really disable or add new classes (with a browser extension) so you can't take full advantage of fine tuning your design in the browser, which makes for a clunky experience imo.

[meriofrog]

When I first started out, I used tailwind and I started to hate it, then I moved on to scss, and then I started to use tailwind again and I fell in love with it. If you know how to use it and get the most out of it, you are going to love it 100%

[tuffilaro]

I completely agree with your analysis! Tailwind is great for components, but when making a pure HTML based site, I can understand that people might not like the "messiness" of it. In that case I would still recommend using something like SASS over plain CSS, to clean up the code even more if you prefer that.

[obelisk.]

I don’t hate it and it seems useful. I just like being able to create elements liberally without having to alter any framework classes.

[ryanleemartin]

I don't know. I find that the more I learn about CSS the less I like tailwind. I find tailwind becomes more unnecessary when building components like with svelte. It's just not that hard to write scoped css. I'm on the fence. It does get you started quickly and copy pasting a pile of stuff that looks good from the jump is nice. But these shortcuts can prevent you from really learning CSS which is the best investment and worth your time.

[saburex]

Why would I fill my components with garbage classes instead of using clean style objects🤷‍♂️

[stevenismart]

If there are no wireframes and I'm just freestyling it, I use TailwindCSS to quickly set up a layout. Then I go back and start organizing the components and add classes. When you have a better idea on how you want your site to look like, you can name the classes and components better. Using typescript prevents any simple mistakes along the way.

[gorilla-san]

I agree with most of this stuff, but what do you mean 'responsive by design'? You literally have to set styles manually for every breakpoint. The only thing I've seen that's responsive by design is the container class.

[ehvenga]

as a developer I love it to the extent I don't approve vanilla css unless it's extended through tailwind.

[sultonbekrakhimov]

I love it, cuz it's trade between clean html template file but complex css rules and a bit ugly html but all rules in it, I choose the latter because it's easier to build middle sized websites without time wasting by trying to find common css rules between components, for large applications maybe writing your own css rules and using presets is good

[akanahketo]

I would like to use NextUI, but... it has TailwindCSS.