[MichaelMug]

Most of the devs I've encountered that really like Tailwind have their focus more in the realm of development and engineering of a whole system where the UI is a means to an end. They are not deeply focused into the nuances of user interface design.

I can understand and appreciate what Tailwind is all about. It's a standards approach to naming conventions and puts all the details in the markup. Which has its value.

I've found a happy balance to be:

1. utility classes for layout and structural details

2. custom classes for look/feel details

3. after x utility classes, its time to combine into a single class

x is very much based on situation and intuition not a hard rule.

I'm still using LESS because of nested css, and classes can be composed.

One benefit of LESS is the style code is decoupled from react/angular components and more importantly the shadow dom.