5 ms·

I do, and it’s great having the styles right there and hackable.

• recursive 1y ago
  How can styles ever not be hackable? Inline styles always take precedence. What can ever stop you from slapping in more inline styles?
• ericwood 1y ago
  To be fair, this is the case with any styling approach; if the style is applied to the element, it's there for you to toy with in the inspector.
• thaumasiotes 1y ago
  Huh? You have the styles right there and hackable regardless of your tooling. That's what browser inspectors do.
• pheres 1y ago
  No matter what you are using, they are always there, editable/hackable. However I would argue that it makes it slightly harder to make any change. You no longer have a single class with all the styles that are affecting that element. You can change the classes in the harder to read html, or override the single element. There is no longer the possibility to, for example, affect all .primary-btns.
  • phatskat 1y ago
    > You can change the classes in the harder to read html, or override the single element. There is no longer the possibility to, for example, affect all .primary-btns. Sure there is, the only thing is that instead of having 20 <button class=“primary”> tags, you have a <ButtonPrimary> component. Change the component once, and all instances get the update. This applies regardless of Tailwind. But if you’re repeating classes on the same kind of element over and over, then the question is less about how you’re styling it and more about how you’re organizing things.