Great question. We rarely rely on shared utility classes these days. Historically we'd end up going the @apply route, but lately we just add a new style to the root-level css file and call it a day. We may prefix it with "@layer" so that it gets tree-shaken, but that's about it.
I've found that in component-driven UI, the need for these kinds of utility classes becomes less and less necessary. The utility CSS may be defined in the component, and the component is ultimately what gets reused.
Could you elaborate more on the reason for your interest? I've used Tailwind to implement several well-defined design languages, and always had great success. In fact, compared to other design systems, Material for example, I found it to be far simpler to manage over time.
I’m a strong advocate for Tailwind, and I believe that this approach is truly effective. In my experience, this subset of Tailwind has been sufficient for every project I've worked on that used it. Moreover, I've observed that it often converts skeptics into supporters.
Mostly echoing everyone else’s appreciation for the film in the thread. I was sucked in when I saw it the first time, and it’s one of the few movies I regret not seeing in theaters when it was available. If Alamo ever decides to do a special showing of it, I’d be there in a heartbeat.
It’s upsetting how as the years go on, I’m seeing more and more similarities to the world that the film depicts. But in a strange way, that makes the film all the more important to me.