Great example of "when switching to a different general purpose allocator affects performance, your memory management strategy sucks".

The Rust compiler seems to do an absolutely insane amount of heap allocations.

(from: https://sharnoff.io/blog/why-rust-compiler-slow#switching-from-alpine)

Chatting to someone who seems to be obsessed with 'boosting' their immune system.
"You can make your immune system work harder by doing this and getting it to 110%"

Sir, if my immune system is working 110% that is called an autoimmune disease

Sent a pull request to Audacity fixing a crash bug I'd been running into frequently. The cause was an out-of-bounds memmove. Classic C++ areas.

Anyway I got a fucking copilot review on my PR which left two comments, both completely wrong, one of which suggesting I reintroduce the out of bounds memory access. I'm furious!

Today in vendors slipping single bits (or single bit!) of information into weird places:

I am *completely* certain that Google once made a USB-C audio adapter that has a *different USB PID* depending on whether it has something plugged into it.

I am somewhat certain that it's 18d1:5025 with something plugged in, and 18d1:5029 without.

If anyone has this adapter and is interested in this useless research, please send screenshots lsusb or device manager for this. Thank you so much. I need this.