Frontend

In hindsight it was inevitable. Type-safe functional programming is coming to CSS.

This means cascading property definitions will no longer just be bound by plain rules, cascade `@layer`s and `@media` queries, but any arbitrary composable hierarchical structure you wish.

In hindsight it was inevitable. Type-safe functional programming is coming to CSS.

This means cascading property definitions will no longer just be bound by plain rules, cascade `@layer`s and `@media` queries, but any arbitrary composable hierarchical structure you wish.

https://www.bram.us/2025/02/09/css-custom-functions-teaser/

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

@day---break, day---break.com // nf.td/iam

https://warpcast.com/iammatthias/0xa64b538f

Jack of many trades, master at being human. 

nkem.dev

 /learninpublic /true

Yes! I could definitely see people using this to come up with new “methodologies” much like BEM, OOCSS or Tailwind that came before. In this case, restricting `@function` usage to only pure functions could allow you to avoid cascade overrides.

tbh, this feels like a natural evolution, but do you think this lead to something like 'pure CSS functions' where the output only depends on the inputs, regardless of cascade context?. Because all I can think about is how it affects the cascading nature of css