Agree the market is weird right now, but on that specific example - TailwindCSS was built around the notion of reducing keystrokes per style (basically). That's not as useful in the age of AI, of course. CSS-Tricks is about learning what modern CSS can do, which is arguably still useful. An uphill battle, for sure, but I think there's still a place for hand written human content on the web, so I plan to support it even if it's just with my clicks.

▲

Tadpole9181 2 hours ago | parent [-]

> TailwindCSS was built around the notion of reducing keystrokes per style (basically).

That "basically" is doing a lot of heavy lifting.

I don't even use Tailwind and I know the point is to localize basic style information and reduce the amount of weird CSS you have to write via functions and utilities.

Especially because Tailwind came well before CSS started natively having these features (let alone them becoming baseline widely available).

Both of those goals definitely help the current era of agents by making it easier to find the rules that affect an element without needing to reliably search all of the project CSS, and reducing required context use and the need to keep track of selector lists.

▲

danielvaughn an hour ago | parent [-]

By localizing basic style information and reducing the amount of weird CSS you have to write, you have thus reduced your keystrokes per style. We're talking about the same thing.

	▲	Tadpole9181 an hour ago \| parent [-]
		No, the semantics are different. The goal has never been "type less", which changes how it interacts with your premise. The goal has been reduce cognitive load and increase semantic density and discoverability. And, counter to what you said ("that's not as useful in the age of AI"), those are very useful in the current age of AI.