- From: rgembalik via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Sep 2024 08:17:09 +0000
- To: public-css-archive@w3.org
I think I prefer `display: masonry` for the following reasons: 1. with `display: masonry` there would be no cognitive complexity while reading and parsing the CSS - it would spell right out the masonry layout used. With a grid, you would have to analyze grid parameters and translate them to how they work with masonry. 2. The grid is already complex enough and adding a masonry layer to it will further complicate things. I teach less experienced developers quite often and I already can see some learning friction on grid syntax, especially with functions that work only on grids. 3. grid is about - well - grids. Masonry steps outside of that, at least in one axis. I know, it's a loose comparison, but I think it's a similar case with flex, which is a separate display. 4. Any feature added to grids in the future would have to be separately explained in terms of how it works with masonry. My gut feeling tells me, that it would lead to more confusion. -- GitHub Notification of comment by rgembalik Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2365056752 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 21 September 2024 08:17:10 UTC