I had a lot of fun with ChucK back in the day, really nice system.

The buried important part:

"It’s absolutely crystal clear that there are benefits of protein to muscle growth and exercise response of active individuals," study author Dudley Lamming said in a statement. "But because most people are relatively sedentary, many people are likely consuming more protein than they actually need, which probably has negative health consequences."

[/me proceeds to have more protein and keep working out.]

Seems like “probably has negative health consequences” in the article is missing “ceteris paribus” (negative when remaining sedentary).

Well, if they can assume you’re probably sedentary they’re probably right.

Yes. On Apple Silicon Macs (w/ macOS Sonoma or later), native fullscreen automatically triggers Game Mode. This feature slashes input lag by prioritizing CPU/GPU resources and doubling the Bluetooth polling rate to 240 Hz for wireless accessories. Gaming works very well in this mode, even with PC titles played thru crossover.

Conversely, using borderless windowed mode instead of native fullscreen on macOS adds rendering latency due to the Desktop Window Manager (DWM) compositor. The latter is 'doing it wrong' and has the lag people don't like.

I didn't know that part about the bluetooth polling rate. That's clever.

macOS doesn't have Desktop Window Manager, it has WindowServer.

Game mode also breaks background audio playback through Bluetooth. And it's hard to turn off with no global setting. I hate it.

I have this problem a few times a day on my corporate M4 Pro when I lock the screen... with 60Hz set. It happens when the two security monitoring app corporate insists on are scanning harder b/c the screensaver kicked in. My personal macbook pro is fine.

My employer does, and 10 digits. (very large software company)

Supply chain at volume makes it hard to to little else.

Uptime of 13 days. My WindowServer is at 441Mb. ??? (32Gb RAM M2Max MBPro)

I first ran xneko in 1990. Was my vibe that year in uni.

Have had iPhones since the 5s. On a 17pro now. Never had this happen as an apple software thing, but the new ones (I last had a 14 and didn't have this problem, not sure when the button placement changed) make it easier to accidentally place the user's thumb on the volume buttons (up -or- down) and end up cranking it or silencing it unintentionally.

So _that's_ how the coyote sourced them.... ;)