DEV Community

Discussion on: Debunking Tailwind Counterarguments

Collapse
 
pavelloz profile image
Paweł Kowalski • Edited

I think most people that argue and try to depreciate Tailwind are either
1) purely theorethical in the long-term maintenance of a project
2) never worked in a project with more than one FED for over a year

In both cases it boils down to being unexperienced and they just need to live through the pain of a css maintenance on their own, until then, they will try to convince the world that some utopian vision about "concerns" is more important than being able to work without rewriting the frontend every 2 years or spending 10 hours a month solving css conflicts. They will learn, CSS and time is a very good teacher of pragmatic programming :)

Collapse
 
jannikwempe profile image
Jannik Wempe

Agree.
You will experience some things only by trying it. I mean it's more obvious the HTML looks somehow bloated then something like the maintanability over time being increased.

Collapse
 
pavelloz profile image
Paweł Kowalski • Edited

Well, bloat in html by adding classes is far easier to maintain in a team than a file of global css classes. ;) CSS being global is the worst thing about the whole environment, and Tailwind fixes that issue without adding 100 different languages, dependencies and doesnt force anyone to use some weird frameworks to achieve good performance - its by default.