News for hackers. Stuff that matters.
Re:Creators of Tailwind laid off 75% of their engineering team by spoiler on Wednesday January 07, 2026 @02:35PM (#46531352)
> and nobody knows what is going on there.

For what its worth, I had the same experience with Tailwind. I regularly see classes that don't have an meaningful outcome.

I don't think the problem is Tailwind or CSS (well, I guess Tailwind is CSS with extra steps but you get the idea) syntax (or any of the CSS preprocessors), but the fact that styling in browsers has accumulated a lot of cruft, and people who haven't "grown up" with it over the years don't fully understand it (I am more competent than most with it and there's still times I screw up).

One thing that's kinda nice about Tailwind is that it made copy-pasting components easier. So people can get something decent without fully understanding what's happening

Re:Creators of Tailwind laid off 75% of their engineering team by koakuma-chan on Wednesday January 07, 2026 @02:44PM (#46531497)
> I regularly see classes that don't have an meaningful outcome.

You mean custom classes?

Re:Creators of Tailwind laid off 75% of their engineering team by spoiler on Friday January 09, 2026 @05:43AM (#46552371)
I mean stuff like adding `display: block` on the parent and `flex: 1` on a child element. Clearly a copy-pasting leftover because someone or whatnot, but then you're debugging a layout issue and you're wondering "but why is this here"