Why not? This wasn't found by source review. The computer was slow, somebody looked into why. The bug was discovered via analysis of binary artifacts, and only then traced back to the source. Bruce Dawson does this all the time on Windows.
That article is very confused. They're saying that transglutaminase, street name meat glue, extracted from bacteria is literally the same thing as pink slime. Lean finely textured beef, street name pink slime, comes from cows. However processed, it's still beef. You can't squeeze it out of bacteria.
Reading the Wikipedia articles it's pretty clear these are different things, even if both are added to beef in some way.
Do you have a source for transglutiminase used to put the pink slime back together? This is the first I'm hearing it. I thought they just stirred it into the ground beef.
> Note that as these machines have not been released for general availability yet, supported and missing features are predictions based on what Apple has changed on a per-SoC and per-machine basis in the past. This page will change rapidly once work begins on support for these machines.
These machines have been available for quite a while.
I just ran cargo check on nushell, and it took a minute and a half. I didn't time how long it took to compile, maybe five minutes earlier today? So I would call it faster, but still not fast.
I was all excited to conduct the "cargo check; mrustc; cc" is 100x faster experiment, but I think at best, the multiple is going to be pretty small.
The game is man vs machine. The machine fills the space with blocks; the human clears space for the blocks. The machine wins when the human fails to make room for the next block. The human wins when the machine fails to deliver the next block.
Shipping a VM would have simplified things, but nobody did that, and nobody was going to download that. For Linux, we packaged everything we could, but it was still bring your own MySQL, and people had all sorts of terrible configs.
And it was kinda pre-cloud, so usually we got provisioned on some pentium ii forgotten in a closet.
I am always happy when I look back on the monobugz days. I think it was a formative experience in evaluating claims like well, of course it works, so many other people already use and depend on it. O RLY?
It's a really weird complaint. The standard specifies that it's now undefined behavior. That imposes zero requirements to change the library. Whatever it is the library was doing, it's one possible undefined behavior.
900 years ago there was a CPU which stored pointers in special registers and trapped if you loaded a pointer with an invalid segment. And so loading the pointer into a register to compare it would crash.
https://arstechnica.com/gadgets/2025/12/steamos-vs-windows-o...