DEV Community

Discussion on: My first experiences with Tailwind CSS

Collapse
capsule profile image
Thibaut Allender

OK I'll help you: Tailwind (or any utility css framework) is just going back to inline styles. Ugly HTML, no separation of content and presentation, the need to learn tailwind. what happens when you need custom css or want to overwrite something that you don't like in tailwind? You still need to write custom CSS anyway. It just makes no sense, never has, never will.

Thread Thread
dailydevtips1 profile image
Chris Bongers Author

Yes that is exactly my feeling so far.

I mean don't get me wrong, it's cool and I was kind of over bootstrap because you have to re-do most of that anyway.
But compared to pure CSS I don't see any real strength, especially in component-based systems...

Why do you think it has such a high adoption, fan base?

Thread Thread
capsule profile image
Thibaut Allender • Edited

The prospect is attractive to junior developers. They think CSS is difficult so anything that allows them to write as little CSS as possible is a massive win. So instead of using that precious time learning CSS, they learn tailwind. What’s even worse is when they used bootstrap before; imagine all these years learning frameworks while they could have learnt a core knowledge instead. It blows my mind and makes me really sad.

Thread Thread
dailydevtips1 profile image
Chris Bongers Author

True indeed, let's hope a trend will come where we just go back to vanilla js and plain css then :D

Thread Thread
capsule profile image
Thibaut Allender

Mate, it's up to you only to follow the trend you feel is the right one, but generally speaking, trends in development don't last long. Be a craftsman, don't let the brand new shiny tools get control of yourself.