Frontend

CSS is literally a domain-specific language purpose-built for logic.

Selectors, media queries, container queries, `:is()`, `:not()`, `:has()`, `@supports` — all in service of helping you quickly define what styles do or not apply at the CSS rule level.

It’s about time we had this at the CSS property level too.

I like tailwind but

what makes it valuable is being able to define co-locate styles with markup (and in React with JS) and avoid naming things

but if CSS had property level modifiers we could just do this with CSS and remove a leaky abstraction 

I mostly like using tailwind arbitrary at this point anyway, especially in a component based framework where things like padding and colors can be centralized in components or constants

Building @warpcast and @farcaster, new dad, like making food

if I was setting up a front end project tomorrow I would use tailwind 

nix all the default colors in favor of a few semantically themed ones (text-primary) and sizes for padding, margin, height, widths in favor or using arbitrary values in components and constants