3 ms·
This is very well-trodden ground at this point, but the reasons people use and like Tailwind have nothing to do with an unwillingness to think or name things.
by monooso 3y ago
This is very well-trodden ground at this point, but the reasons people use and like Tailwind have nothing to do with an unwillingness to think or name things.
You're welcome to use whatever works for you, but don't assume that anyone who prefers an alternative approach is mentally lazy.
- agos 3y agonot having to name things is one of the main selling points for Tailwind, and frequently repeated in discussions about Tailwind
- rendall 3y agoI agree that dev-shaming is a reality of our industry that must be abandoned. Use Tailwind if it works for your use case. That said, I am amazed at the sheer industrial levels of effort that devs go through in order not to learn and use CSS. It's a pretty nifty solution to the problem of programming layout and interfaces.
- monooso 3y agoI spent over 20 years writing CSS, trying countless naming conventions and organisational techniques in an attempt to keep everything clear and maintainable. I don't miss it, but to each their own.
- rendall 3y agoCSS can be complicated because the problem it solves is complicated, not because it is a bad solution. Using a more constrained CSS is completely valid if it works for your project.