Re: [csswg-drafts] Alternate masonry path forward (#9041)

For me, this all boils down to the question of whether CSS syntax should be based on "What" it's doing, or "How" it's doing it.

When I say `background: black`, then switch it to `background: linear-gradient(45deg, black, white)`, it doesn't matter to me HOW the browser is implementing that instruction... I’m simply telling it what I want it to look like. If the browser has to switch to an entirely different rendering approach to implement that instruction in a performant way, that’s a problem for the browser dev, not the CSS dev.

Creating `display: masonry` as a totally separate thing because of implementation concerns feels like it goes against this principle... it’s making me think about HOW the browser will perform my instructions, rather than WHAT I want it to do.

However I can appreciate the arguments on both sides, and ultimately I care more about getting SOME form of this I can use than I do about getting perfect syntax. Heck, the flexbox syntax is ridiculously confusing (I never know whether I want justify or align) but I’m still really glad we have it.

-- 
GitHub Notification of comment by chrisarmstrong
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2095928556 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 6 May 2024 12:40:48 UTC