I partially disagree with you here. The power of Tailwind CSS comes when you need to make small and specific changes (such as spacing, sizing) in certain parts of a UI.
Rather than writing specific styles for a button that needs to be slightly larger in a certain place, it's easier to add a utility class to it right away.
Of course, it is good to have reusable classes for elements that look more or less the same, but it can be bothersome to always switch to the CSS file and create a new class or modify an existing one just to add a few more pixels in spacing, sizing, and so on.
just because it is easier it is not better, you will produce unreadable gibberish and save like 5 seconds of your time, which you will lose eventually by trying to understand your code a few months later
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
then there is no point in using tailwind anyway, you can just write regular css and achieve the same results with the same amount of code
I partially disagree with you here. The power of Tailwind CSS comes when you need to make small and specific changes (such as spacing, sizing) in certain parts of a UI.
Rather than writing specific styles for a button that needs to be slightly larger in a certain place, it's easier to add a utility class to it right away.
Of course, it is good to have reusable classes for elements that look more or less the same, but it can be bothersome to always switch to the CSS file and create a new class or modify an existing one just to add a few more pixels in spacing, sizing, and so on.
just because it is easier it is not better, you will produce unreadable gibberish and save like 5 seconds of your time, which you will lose eventually by trying to understand your code a few months later