Eduardo Laranjo
@eduardolaranjo.bsky.social
Reposted by Eduardo Laranjo
I'm launching a new Go-related series named Accepted.
For each accepted proposal, I'll write a one-page summary that explains the change in simple terms.
This should (hopefully) be the easiest way to keep up with upcoming changes.
The first issue is already out!
For each accepted proposal, I'll write a one-page summary that explains the change in simple terms.
This should (hopefully) be the easiest way to keep up with upcoming changes.
The first issue is already out!
September 24, 2025 at 12:21 PM
I'm launching a new Go-related series named Accepted.
For each accepted proposal, I'll write a one-page summary that explains the change in simple terms.
This should (hopefully) be the easiest way to keep up with upcoming changes.
The first issue is already out!
For each accepted proposal, I'll write a one-page summary that explains the change in simple terms.
This should (hopefully) be the easiest way to keep up with upcoming changes.
The first issue is already out!
Reposted by Eduardo Laranjo
In an episode that’s arguably 2 years overdue, @bcantrill.bsky.social and I were joined by John and @sunshowers.io to talk about finding and debugging a bizarre data corruption bug whose cause had its roots in CPU speculation—maybe the craziest bug I’ve seen!
youtu.be/Nq7ranhHXwA
youtu.be/Nq7ranhHXwA
Oxide and Friends 7/7/2025 -- Adventures in Data Corruption
YouTube video by Oxide Computer Company
youtu.be
July 9, 2025 at 2:12 PM
In an episode that’s arguably 2 years overdue, @bcantrill.bsky.social and I were joined by John and @sunshowers.io to talk about finding and debugging a bizarre data corruption bug whose cause had its roots in CPU speculation—maybe the craziest bug I’ve seen!
youtu.be/Nq7ranhHXwA
youtu.be/Nq7ranhHXwA