4 ms·

I think the point in the comment you are replying to is that they _prefer_ having markup and styles in separate files.

• solumunus 4y ago
  You can still do that though. I swear half the Tailwind haters haven't used it for more than 30 minutes, or at all.
  • xigoi 4y ago
    Then what's the advantage of Tailwind?
    • solumunus 4y ago
      Standardised and clean CSS syntax. The benefits in that context are debatable, a component based frontend architecture is where it absolutely shines. If you end up using it in that context you won't need to ask this question, it quickly becomes clear that it's the optimal path.
      • emmacharp 4y ago
        What can't pure CSS do here and that Tailwind does ? The CSS syntax is already clean and standardized if you use it properly and don't name every little piece of interface. It is a genuine question, by the way...
      • xigoi 4y ago
        CSS is standardized…
• nailer 4y ago
  No, I have HTML and CSS in the same component file. I prefer having styling in one place (the CSS inside the component file) rather than two (the HTML of the component and tailwinds’s own postcss files that implement the styles).