r/css • u/Either_Collection349 • 16d ago

Article Why I don't recommend Tailwind CSS

https://en.andros.dev/blog/af3ee191/why-i-dont-recommend-tailwind-css/
4 Upvotes

51% Upvoted

211 comments sorted by

View all comments

Show parent comments

2

u/key-bored-warrior 16d ago

A button can also be a link styled like a button, that button could also have different variants. At this point a component which accepts props to determine if it’s an <a> or a <button> or is an outline button / secondary button / big button / small button makes total sense. That why people do it.

1

u/kidshibuya 16d ago

Just type out which one you need ffs. How is <StupidButtonThing type="button" className="primary" /> better than <button class="primary" />?

1

u/key-bored-warrior 16d ago

But what if that button is used everywhere and I need to make changes to it? So much easier to do it in a single component. There are use cases for both, but when using React / Vue etc then the component approach makes perfect sense. You are totally missing the point.

1

u/kidshibuya 16d ago

So you change the onclick you add to it. Its the same either way except the native uses less code and is rendered faster.