Often, you are better off with a single standard environment rather than one with a hodgepodge of locally optimal solutions.
replyHum... You want to say that tailwind is that standard, and some place can just avoid any css by using it?
replyYou want to say that there shouldn’t be standards because tailwind has limitations?
replyDepends on who "you" are. A project manager might be better off. An individual contributor is probably better off using the right tool for the job.
replyYou can put tailwind on the CV
replyWhile I understand your overall point your example of tailwind just seems odd. The idea that a css library makes or breaks what a project is capable of is kinda... IDK... laughable?
replyWhat is the challenge in downloading class names into a style directory?
> The idea that a css library makes or breaks what a project is capable of is kinda... IDK... laughable?
replyThen you didn’t understand my point, because it didn’t make or break a project. Making or breaking a project wasn’t my point.
Who works with Tailwind? The dev writing code or the product person demanding that Tailwind be used in code they’ll never maintain or even look at?