When will CSS Grid Lanes arrive?(webkit.org) |
When will CSS Grid Lanes arrive?(webkit.org) |
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.
+-------+------------+ +-------+------------+ +-------+------------+
| state | population | | state | population | | state | population |
+=======+============+ +=======+============+ +=======+============+
| AL | .... | | DE | .... | | MI | .... |
| AK | .... | | FL | ..... | | MN | .... |
| | | | | | | | |
I dislike the idea that CSS should be made more complex. Everyone is doing the same template with Jumbotron anyway.
Pick the colors, pick imagery and name for the brand - doing some magic with CSS will only piss off people.
Cookie cutter design is what I like. I can compare the companies when they all have the same template for a website.
curious how this works, huh.
seems like the same institutions starving to push browser updates are also authoring standards.
>who need to keep things fast and responsive reality says otherwise. but they definitely need to push updates.
Grid covers a lot of very subtle use cases that have historically required hacks like a list of select options where some can have icons on the left and some don't. You just need a subgrid that will automatically position every element in the select correctly to align them, regardless of whether there is an icon or not within the element in all select items. Previously you'd have to add a fixed width padding to the left and check if all the select items had icons. It also correctly scales the width and height of a row of items like cards where you want to ensure the alignment of headers, content, image etc depending on if that stuff is in there or not. You can have text missing and the card will still take up that size because your subgrid has defined it so. All of this needed JS, complex CSS hacks and so on. These aren't obscure features these are commonly used layouts that required a lot of time and effort to make it look nice.
[1] https://webkit.org/blog/17660/introducing-css-grid-lanes/
Here's an old all-tables site of mine.[1] Try resizing the window. Works fine. It won't narrow down to mobile dimensions well, though.
Any reference?
Also I do feel like some people prefer animations. Maybe not the Hackernews crowd itself per se. But I think that having two options (or heck three the third one being really just pure html just text no styling maybe some simple markdown) is something good in my opinion.
Honestly I do feel like 1-2 animations are okay with a website but the award winning websites really over spam it in my opinion
I think maybe the amount of animations in https://css-tricks.com might be nice given that those guys/website teaches other people about animation themselves and have only 1 maybe 2 animations that I can observe interacting with their website and I do feel like that's for good reason (they don't want animations to be too distracting)
I personally don't know, I personally have never built any such websites but recently wanted to and I was looking at gsap tuturials on today & I do feel like one of the frustrations I feel is that these animations don't respect the browser sometimes to have animations (Scroll animations being the first one) but I even watched some designers talk about how much important scroll animations are (them betting that every award winning website has scroll animations)
Even https://ycombinator.com has a lots of animations & Css features & people on HN did love it from what I could tell. So to me, it does feel as if there is no one size fits all.
Also, if everyone is implementing the same Jumbotron design again anyway, why not standardise that and support it right away instead? That’s how we got a bunch of features recently, like dialogs, popovers, or page transitions. And it’s for the better, I think.
A strong reason to use llms today is accessing plain text information without needing to interface with someone else stupid css. You really think the general sentiment around css is: yay things are improving?
another strong reason to use llms: no needing to write css anymore.
And that being said: the ability to express something in a single CSS directive as opposed to a special incantation in JavaScript is an objective improvement, especially with LLMs.
general sentiment is quite relevant when discussing standards but maybe it was a mistake to reply to your comment and not address this point in parent