htmx

I mean, I'm on 1440p and 4k monitors here and the text is still quite massive even on the high density screens.

Even 0.8rem is quite big, but at least it fits all the content in a readable way

https://coderthemes.com/hyper/saas/index.html

I think for docs a sidebar nav w/ the right side being flex is a pretty good setup

Well in the very short term it should be changed a bit so it isn't just a tower of chopped up text.  It's not a good situation to leave it as it is.

For those following, <@249837723416788992> and I deployed a quick patch to resolve it the other day. So all good for now.

https://developer.chrome.com/blog/help-css-nesting/ looks like css nesting might be standard soon

tbh I think the poll is a joke from google in order to railroad everyone into their choice.

The other options are pretty obviously bad

Not saying `&` is bad, but ya... it's the only realistic choice

if they are obviously bad then why would they need to railroad anyone into anything

illusion of choice man idk, google has an image to keep up.

we web developers overestimate how much google cares about trivialities of syntax

well if you have a better idea the discussion is on github https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-924118287

although the css working group already discussed these three options it seems, so i'm not sure they'll open the subject again

`&` is fine man, I just think given the position that google is in, they should have put a bit more effort into it.

https://tenor.com/view/i-voted-sticker-sticker-i-voted-by-mail-thumbs-up-vote-gif-18160788

I don't understand the `&` within the "brackets" syntax - wouldn't brackets imply nesting?

at this point, I unconditionally and violently support anything that breaks the SCSS hammerlock on the industry

ikr. they really should have touched on this more and explained why this was a no-go.

I still think inlining the `&` is the most straightforward. Most CSS I've seen has the bracket at the end of the line with the selector (Java style), but their examples had the nesting brackets on a new line (C# style). It looked awkward, and combined with the seemingly-unnecessary `&`, it's one I'd actively root against.

(And why are we calling braces "brackets"? But I digress...)

https://twitter.com/Una/status/1554838542836195328

insane update, safari already has it too, firefox soon