Why I Like and Don't Like Tailwind CSS

I'll explain why I like and don't like Tailwind CSS.

In a word, Tailwind CSS is in the right direction, but not the final cure in the JavaScript Web App world.

Here is my youtube video explaining this: https://youtu.be/Nww06Z5wkKY

Transcript

1. Why I like And don’t like Tailwind CSS.
2. Let’s see the concept of Tailwind
3. Link is in the description
4. 1. Semantic CSS is bad Agree
5. don’t like this too.
6. 2. We prefer composition over duplication. Agree
7. 3. After several phases Utility CSS is the cure Agree
8. Much Better Than Semantics
9. 4. Enforces consistency Yes, but we can also achieve this in another way
10. I agree on most of the claims Now is something I don’t
11. It is just a syntax issue, maybe true for pure HTML/CSS But not true for JavaScript Component
12. Tailwind is improved “inline style”
13. Tailwind doesn’t mention Its own cost of New Layer over CSS.
14. Tailwind adds new syntax to string (class name), new dialect to CSS, But you still needs to understand CSS, It is overwork not less.
15. I love the idea of “utility” But it is just an idea, CSS is not a must.
16. Why not just *give up* CSS? Like Flutter/SwiftUI
17. Atomic style Or Component style Elegantly declared!
18. Tailwind Just a rough Functional idea 1. No handy shorthand 2. Just JavaScript Function Syntax 3. don’t care about CSS
19. Declare only local styles With least effort. Let programs do the rest.
20. Parse Optimize Generate any CSS(even Tailwind) you want
21. Summary
22. Tailwind is on the right direction.
23. Good for HTML/CSS, But for JS components, It is not the fi nal cure.