Divitis was a thing long before React came along. It was a common solution to styling problems even in the jQuery/Dojo days. Getting stuff to look similar across IE6 and FF before CSS3 relied heavily on divs.
replyIt did for sure. And Tailwind absolutely doesn’t need to be done this way. I think this is a correlation-not-causation issue
replyI disagree. With Tailwind you think in nested classes which ergonomically encourages “I need a div for this class”.
replyVery 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.