Purely from experience — largely, design system or development projects at large organisations are lead from a PMO, design or product teams — with technology of

Purely from experience — largely, design system or development projects at large organisations are lead from a PMO, design or product teams — with technology often seen as down-stream (at least, in terms of development, there is of course technology architecture/advisory along the way.) That means that the design/product requirements come first. The moment Tailwind's limitations meet design requirements, it'll take a back-seat. It's basically the same reaction you'd encounter from saying "we'll build it in Bootstrap." If a company is investing in a new product or service, no one wants to be the guy that says "sorry our framework won't let us do that design" — at least, not in first year or two of a product life-cycle. Tailwind's advantage — speed and accessibility for a range of developer backgrounds — isn't the same priority for large organisations vs. startups.