[moritzwarhier]

I moved away from using it but I guess you underestimate the intellectual capabilities of people using it.

How you want to write CSS is a tradeoff.

Traditional CSS without tools like Tailwind, styled-components or other "hacks" is especially bad at collaboration and evolving from prototypes to large sites or apps, in my experience.

[tehbeard]

They arent dismissing the users of tailwind's intellectual capacity.

They're attributing a cult like / social influence phenomenon to the popularity of it. That others use it because others use it; not on any perceived by them actual merit of tailwinds design.

[moritzwarhier]

I was basing my comment on the perceived assumption that this would be the only possible reason to use it.

I was convinced to try it by Adam Wathans initial blog post comparing it to BEM notation and "semantic" class names.

The arguments in that blog post still make sense, regardless if you think that tailwind is a good solution.

A cult like / social influence phenomenon is attributable to a lot of tech. Not sure if I'd call that "mass psychosis" though.

Sure, Tailwind tends towards lock-in, it also adds complexity in other places. It also will surely go out of fashion soon, or already has.

But it brought a concrete idea to the table, which worked for many people, and that was the reason for the "hype", in my opinion. Not "mass psychosis".

I never wanted to use it because of fashion. Maybe that was the reason I got to know about it though.

Also it influenced the way I write CSS, despite not using it anymore. In short: avoid being clever with the cascade, like the plague.

And I mainly stopped using it because I changed my job after 5 years. The projects we used tailwind for went well and it succeeded at avoiding the problems I wanted to avoid, especially when collaborating with a newly hired young colleague.

So yes, it is an example of a hype, might have been overhyped, but that's not "mass psychosis" to me.