thepudds
@thepudds.bsky.social
Go contributor.
Posts tend to be about #golang, performance, fuzzing, and Go Modules. He/him.
https://github.com/thepudds
Posts tend to be about #golang, performance, fuzzing, and Go Modules. He/him.
https://github.com/thepudds
Reposted by thepudds
For some added fun, also see go.dev/cl/715362, wherein I discover that VPCOMPRESSQ is horrifically slow on AMD Zen 4, but only with a memory destination.
And thanks to @lemire.bsky.social for writing about this, which made this much faster to track down!
And thanks to @lemire.bsky.social for writing about this, which made this much faster to track down!
Gerrit Code Review
go.dev
October 29, 2025 at 7:20 PM
For some added fun, also see go.dev/cl/715362, wherein I discover that VPCOMPRESSQ is horrifically slow on AMD Zen 4, but only with a memory destination.
And thanks to @lemire.bsky.social for writing about this, which made this much faster to track down!
And thanks to @lemire.bsky.social for writing about this, which made this much faster to track down!
Reposted by thepudds
I am using it to test our Go modules against the latest versions of their dependencies (with "go get -u") on a schedule, to be notified early of compatibility issues, but without the supply chain attack risk or the Dependabot churn.
October 24, 2025 at 12:59 PM
I am using it to test our Go modules against the latest versions of their dependencies (with "go get -u") on a schedule, to be notified early of compatibility issues, but without the supply chain attack risk or the Dependabot churn.
Absolutely hilarious.
TBH, though, it probably would not have happened with the original TIE fighter ASCII art:
|A|
|V|
Very nice save by cutting over to:
|-()-|
(Maybe the Star Wars wiki needs to be updated too? Is
@markhamillofficial.bsky.social
the admin on that? 🤔)
TBH, though, it probably would not have happened with the original TIE fighter ASCII art:
|A|
|V|
Very nice save by cutting over to:
|-()-|
(Maybe the Star Wars wiki needs to be updated too? Is
@markhamillofficial.bsky.social
the admin on that? 🤔)
October 18, 2025 at 10:29 PM
Absolutely hilarious.
TBH, though, it probably would not have happened with the original TIE fighter ASCII art:
|A|
|V|
Very nice save by cutting over to:
|-()-|
(Maybe the Star Wars wiki needs to be updated too? Is
@markhamillofficial.bsky.social
the admin on that? 🤔)
TBH, though, it probably would not have happened with the original TIE fighter ASCII art:
|A|
|V|
Very nice save by cutting over to:
|-()-|
(Maybe the Star Wars wiki needs to be updated too? Is
@markhamillofficial.bsky.social
the admin on that? 🤔)
Reposted by thepudds
Oh my god it actually worked.
This might be my funniest—but totally serious—cryptography engineering contribution.
This might be my funniest—but totally serious—cryptography engineering contribution.
October 17, 2025 at 10:53 PM
Oh my god it actually worked.
This might be my funniest—but totally serious—cryptography engineering contribution.
This might be my funniest—but totally serious—cryptography engineering contribution.
FWIW, I think at least some of the early conversation about relying on Sec-Fetch-Site in the Go standard library might have happened here on Bluesky.
(@filippo.abyssdomain.expert with @empijei.bsky.social, @jub0bs.com, others...).
bsky.app/profile/fili...
(@filippo.abyssdomain.expert with @empijei.bsky.social, @jub0bs.com, others...).
bsky.app/profile/fili...
I'm looking into github.com/gorilla/csrf to figure out if we could bring CSRF protection to the standard library.
I am 90% sure the secret key is useless: it signs a random token with no metadata, and the attacker can just get and reuse a valid signed token.
Am I missing something?
I am 90% sure the secret key is useless: it signs a random token with no metadata, and the attacker can just get and reuse a valid signed token.
Am I missing something?
October 15, 2025 at 1:50 PM
FWIW, I think at least some of the early conversation about relying on Sec-Fetch-Site in the Go standard library might have happened here on Bluesky.
(@filippo.abyssdomain.expert with @empijei.bsky.social, @jub0bs.com, others...).
bsky.app/profile/fili...
(@filippo.abyssdomain.expert with @empijei.bsky.social, @jub0bs.com, others...).
bsky.app/profile/fili...
(SMP support a ~couple months ago, the gvisor network stack running under UEFI more recently, ...)
bsky.app/profile/andr...
bsky.app/profile/andr...
Screw PXE, this means the entire Go TLS and networking stack is available under UEFI.
In seconds I added DHCP and an SSH server to remotely manage my pre-boot environments.
I see much potential.
In seconds I added DHCP and an SSH server to remotely manage my pre-boot environments.
I see much potential.
Adding networking to go-boot through UEFI Simple Network Protocol.
It took 77 LOCs of pure Go to add the UEFI driver and bridge it to gVisor stack.
It took 77 LOCs of pure Go to add the UEFI driver and bridge it to gVisor stack.
October 1, 2025 at 2:49 PM
(SMP support a ~couple months ago, the gvisor network stack running under UEFI more recently, ...)
bsky.app/profile/andr...
bsky.app/profile/andr...
Reposted by thepudds
If you haven't been keeping up, Go 1.21 reduced overhead from ~10% to ~1%. 1.22 overhauled the format to improve reliability and add information. 1.25 has a built in trace flight recorder. And we have an active proposal (go.dev/issue/62627) for a trace parsing package to enable arbitrary tooling.
proposal: x/debug/trace: add package for parsing execution traces · Issue #62627 · golang/go
As part of #60773 (tracking issue #57175) I've been working on a new parser for the execution tracer, and to save work down the line I've also been trying to come up with a nice API that would work...
go.dev
September 26, 2025 at 7:32 PM
If you haven't been keeping up, Go 1.21 reduced overhead from ~10% to ~1%. 1.22 overhauled the format to improve reliability and add information. 1.25 has a built in trace flight recorder. And we have an active proposal (go.dev/issue/62627) for a trace parsing package to enable arbitrary tooling.