2 ms·
Even for tailwind, I've only ever found it really helpful in react projects. Styling in react has always been a pain, and the recent(ish) solution of CSS-on-JS
by _heimdall 2y ago
Even for tailwind, I've only ever found it really helpful in react projects. Styling in react has always been a pain, and the recent(ish) solution of CSS-on-JS is a horrible solution in my opinion.
Tailwind was designed specifically to solve styling in react so this does make sense, but as soon as you enter the space of wanting more simple tech that has been stable for years you're throwing out react and might as well throw out tailwind as well, it just isn't needed when CSS is back on the table.
Edit: I should have also included here that there is also absolutely nothing wrong with using Tailwind if that's where you are most productive. We're long passed the days of tailwind shipping unused piles of utility classes, shipping is plenty important if that's where your productivity is.