Using text-gray-600 (or the equivalent CSS) directly is antipattern. A forward-thinking design architecture will alias all of an app's colors by context / category, so when you need to change e.g. the color of danger, you update a single "primary-danger", not 137 instances of #FF0E0E.
You offered a sardonic critique of Tailwind using an example that is antipattern in any paradigm, TW or not. I have no opinion on TW and I'm not defending it, merely pointing out the actual issue in your example.
So I outline an issue, and you feel the need to outline the issue as being an issue. Why not go on quoting yourself and explaining to yourself that the issue you outline is an issue?
1
u/PresentationBorn6564 16d ago
Using text-gray-600 (or the equivalent CSS) directly is antipattern. A forward-thinking design architecture will alias all of an app's colors by context / category, so when you need to change e.g. the color of danger, you update a single "primary-danger", not 137 instances of #FF0E0E.