Am I crazy or is this an insane suggestion? I would think typing this out would lead one to think "we have a serious problem. I cant actually recommend this."
To be fair there may be perfectly good ways to re-use styling with tailwind. I'm not a tailwind expert. Although I know its a common complaint. I assume with React making a component to share styles is a perfectly fine solution.
Of multi-cursor editing, the docs say:
>You'd be surprised at how often this ends up being the best solution. If you can quickly edit all of the duplicated class lists simultaneously, there's no benefit to introducing any additional abstraction.
This is no less true for code in general. Can you imagine opting for IDE multi-cursor editing features over putting something into a function? No of course not, because that's absurd.
To be fair there may be perfectly good ways to re-use styling with tailwind. I'm not a tailwind expert. Although I know its a common complaint. I assume with React making a component to share styles is a perfectly fine solution.
Of multi-cursor editing, the docs say:
>You'd be surprised at how often this ends up being the best solution. If you can quickly edit all of the duplicated class lists simultaneously, there's no benefit to introducing any additional abstraction.
This is no less true for code in general. Can you imagine opting for IDE multi-cursor editing features over putting something into a function? No of course not, because that's absurd.