When will CSS Grid Lanes arrive?

Looking at the comparison image between CSS grid lanes and CSS grid 1, the grid lanes example looks....horrifying. It looks like pinterest cancer. It makes the page look like a ragged assortment of random shit. Scannability is grossly impaired. How are you supposed to approach this content? What objective does this mess of a presentation accomplish? What kind of information lends itself to this kind of "masonry-style waterfall layout"?

Here's the famous 2004 article on why tables are bad.[1] Cool people do everything with break and div. The CSS crowd then spent two decades re-inventing tables.

[1] https://www.hotdesign.com/seybold/everything.html

A feature I want, that appearenly was attempted by some browsers but never stanardized. I want to be able to make a table that can responsively fill out columns.

    +-------+------------+  +-------+------------+  +-------+------------+
    | state | population |  | state | population |  | state | population |
    +=======+============+  +=======+============+  +=======+============+  
    |  AL   | ....       |  |  DE   | ....       |  | MI    | ....       |
    |  AK   | ....       |  |  FL   | .....      |  | MN    | ....       |
    |       |            |  |       |            |  |       |            |  

The left side of the first example picture looks to me like four columns laid out using a vertical flexbox each. In fact, it looks like the very example that I saw people using saying "Look how the flexbox layout on the left doesn't line up the text boxes, but on the right the text boxes are all neatly aligned, isn't that nicer?"

I realize that the difference is that the items are laid out horizontally, i.e. photos 1-2-3-4 are all across the top, whereas with vertical flexboxes items 1-2-3-4 would end up in the first column (or you'd have to rearrange your divs taking the flexbox layout into account, which is often impractical).

But the gain from CSS Grid Lanes is not immediately obvious from looking at the first photo, as it's so very similar to the old "left is flexbox, right is grid" examples from when Grid was new.

I wonder when we'll get hexagonal lanes, triangular and Penrose tiling. Rest assured, there will be practically infinite set of features designers would invent. Language designers would do good takubg into account Scheme idea: language is good when there is nothing to remove.

This seems kind of redundant. I would just use flexbox for something like this. Grid is already an extremely rare item for me. I only ever use it when I need to control the overall layout for an app that has to work on a wide range of viewports. I'd never use grid just because it can do clever brickwork.

Did we really need that? I wonder if people recognize how bad the "standard committee" is and that we are held back by them. I can't hold in my mind how many features the web is missing that should be prioritized, I think I'll make a list and start a blog. The web deserve better