2 ms·
It did for sure. And Tailwind absolutely doesn’t need to be done this way. I think this is a correlation-not-causation issue
by ncphillips 5mo ago
It did for sure. And Tailwind absolutely doesn’t need to be done this way. I think this is a correlation-not-causation issue
- TonyAlicea10 5mo agoI disagree. With Tailwind you think in nested classes which ergonomically encourages “I need a div for this class”. Very similar to early React where every component had to return a single real parent element (now you can return a fragment) so people chose div.