Pretty light on details, heavy on fluff. 9.8s to 3.1s was userfaultd + hugepages, 500ms was PS/2 mouse and… where is the rest of the time to get to 400ms?
No, and having that is not required to know output speed nor the effect of thinking, so I don’t see the point in such a superfluous, indirect question.
The actual paper (linked in another comment here) is literally titled “Nonergodicity and Simpson’s paradox in neurocognitive dynamics of cognitive control”. Why they omit it from the blog post version, I’ve no idea.
Non-Shorts can be vertical as well. It works fine, and without the swipe-encouraging UX. If they were “just making long/medium-form videos in portrait now” they don’t need YT Shorts to do that.
DisplayPort 2.1 (which the monitor supports) provides sufficient bandwidth for 7680x4320@60 Hz 10-bit without DSC when using UHBR20. The press release unfortunately doesn’t clarify whether the monitor supports UHBR20 or only the lower UHBR10 or UHBR13.5 speeds. Of course, the GPU must also support that (Nvidia RTX 5000 only at the moment, as I believe AMD RX 9000 is only UHBR13.5).
Enabling Reduce Transparency is a sure-fire way to find a dozen bugs within a few hours. It is always quite apparent no one who is empowered tests it at Apple. At least the padding issue is the one Feedback report I sent that got the “more than 10 similar issues” label so it may actual get fixed.
No idea on macOS, but turn on Reduce Transparency on iOS and there’s tons of padding most of the time, but then sometimes zero padding. And I mean zero. The edges of buttons and text are at the edge of the underlying background. It’s…embarrassing.