[BryanBeshore]

Upvoted.

OP seems to miss the point that most everyone - or at least everyone I know - that uses Tailwind already knows CSS to a large degree. In addition, everyone I work with would rather spend time writing code than messing around with CSS and trying to name classes (great point you make, and I fully agree)

[runarberg]

As a frontend developer I don’t understand this sentiment. I’ve learned to style websites using CSS, so has every other frontend developer, learning CSS is part of the craft, and if you skip it, you don’t know frontend development. Writing CSS is a big part of the job of a frontend developer.

Now if you are a hacker and are hacking together a website, that is fine. You don’t need to be a frontend developer to write a website, and if that is the case, use tailwind by all means. However in a team that maintains a webapp, you should expect there to be a frontend developer, and you should expect them to know and write CSS, if they are the only person on the team that knows CSS, then probably they will take some authority on that, and I would expect them to assert some authority on every code that contains some styling. If a contributor doesn’t know CSS, and writes a poor CSS code, that should be fixed during peer review. A team that is happy-go-lucky with their styles is surely not going to by writing a well crafted web-app.

[subarctic]

What I understand about Tailwind is that it is _meant_ for those frontend developers who understand CSS, and you're essentially writing CSS when you use Tailwind - as opposed to a component library like bootstrap or material ui.

This sentence:

>Now if you are a hacker and are hacking together a website, that is fine. You don’t need to be a frontend developer to write a website, and if that is the case, use tailwind by all means.

Would make more sense IMO if you replaced the word "tailwind" with "a component library"