[righthand]

I hear this, I have been in plenty of meetings where I propose a solution that eclipses most of the project requirements, often for a product person to turn around and say something like “yeah but I like working with X techhnology”, for example Tailwind.

Okay you like Tailwind because you seem to think “p-2” is better than specifying “padding: 2rem;” because when it comes time to tinker with things you don’t want to understand CSS, you want to play with Tailwind.

[clickety_clack]

Often, you are better off with a single standard environment rather than one with a hodgepodge of locally optimal solutions.

[stonogo]

Depends 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.

[marcosdumay]

Hum... You want to say that tailwind is that standard, and some place can just avoid any css by using it?

[clickety_clack]

You want to say that there shouldn’t be standards because tailwind has limitations?

[robotswantdata]

You can put tailwind on the CV

[shimman]

While 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?

What is the challenge in downloading class names into a style directory?

[righthand]

> The idea that a css library makes or breaks what a project is capable of is kinda... IDK... laughable?

Then 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?

[shimman]

Okay then I still don't know your point outside of wanting to take a "stand" against a CSS library.

You need to write more clear + intentional because you aren't clear in what you're saying at all.