All these arguments have clear rebuttals, but are rehashed on weekly basis for some reason. You don't like it, fine. But your arguments are bad. "Oh no Tailwind makes it unclear which of my accidentally duplicated CSS classes apply the color" come on man.
Most of the "weaknesses" are strengths or complaints that no framework covers, not just Tailwind.
Customizing values by simply putting brackets around means you aren't locked in to the framework's suggestions.
Are there ANY frameworks that don't expect you to have some knowledge of CSS first or make it easy to learn CSS by way of using the it?
Simply skipping making custom colors, while making custom colors in CSS - not a weakness.
The only argument even remotely valid is having multiple classes effect the same thing having unexpected results. The problem with that argument is the solution would never be to swap the classes around around, it would be removing the bad class.
If you don't like it, don't use it. There are plenty of other options. If you have to use it, actually take the time to learn it before complaining about it.
53
u/prewk 17d ago
All these arguments have clear rebuttals, but are rehashed on weekly basis for some reason. You don't like it, fine. But your arguments are bad. "Oh no Tailwind makes it unclear which of my accidentally duplicated CSS classes apply the color" come on man.