News for hackers. Stuff that matters.
Re:Tailwind CSS v3.3 by pcthrowaway on Wednesday March 29, 2023 @12:08PM (#35359249)
Yeah, tailwind isn't intended to make it so you don't have to learn CSS. It very much tries to map to CSS fairly directly, so it wouldn't prevent you from needing to learn it.

> I'm just writing the css but in a different way. cursor-pointer class for "cursor: pointer" for example.

The difference is, when writing the CSS yourself you also have to find a way to apply this to the thing you want it to apply to. Which means you have to write your own selector. Which gives you 1000 guns pointed at your feet, and maybe two aimed away from you (and one of those is just the same one that tailwind gives you, but less portable).

Re:Tailwind CSS v3.3 by emmacharp on Wednesday March 29, 2023 @04:05PM (#35362668)
With simple linting, I think, you could make sure to disable the vast majority of these guns. But I care to hear your take about it.
Re:Tailwind CSS v3.3 by that_guy_iain on Thursday March 30, 2023 @06:50AM (#35370713)
> Yeah, tailwind isn't intended to make it so you don't have to learn CSS. It very much tries to map to CSS fairly directly, so it wouldn't prevent you from needing to learn it.

For me, a framework should deal with the basics and make thing easier. Making it so you just write css differently seems odd for a framework. It seems more like a css parsing framework than anything. The tailwind UI seems like a framework that provides you the basics.