The production bug that made me care about undefined behavior. New blog article fresh out of the oven. gaultier.github.io/blog/the_pro... #cpp #bug

New blog article! Detecting goroutine leaks with DTrace: gaultier.github.io/blog/detecti... #golang #dtrace

Rant: if you are designing a programming language from the ground up and the only solution you have for data races is “use the runtime race detector”, then you have not spent enough time in the trenches suffering from data corruption and rare, incoherent errors due to data races.

New post: a defense of lock poisoning in Rust. Followup to recent discussion: decided to write about lock poisoning, looking at the arguments on each side, and informed by our experience at @oxide.computer dealing with the parallel problem of unexpected async cancellations Please give it a read!

Tracking and fixing many Go data races lately, I am getting a new found understanding and empathy for all these Mozilla developers who jumped on Rust the moment it was halfway usable. Like a lost, thirsty traveler in the desert seeing an oasis from afar. #golang #rust

A million ways to die from a data race in Go. New blog post. Well it’s not quite a million, but still. gaultier.github.io/blog/a_milli... #golang

After many years of writing Go professionally and tracking very varied data races, I am slowly becoming convinced that if you care about data races, you should not use goroutines. At all. #golang

“Hell is other people”. Sartres clearly did not have to support 4 different SQL databases in the same codebase at scale. Lucky bastard.

More DTrace, more Go, more blog articles! gaultier.github.io/blog/how_to_... #dtrace #golang #bug

And another blog article, once again about Go and DTrace: gaultier.github.io/blog/go_dtra... #dtrace #golang

I just wrote another Go + DTrace blog article! This time: Are my SQL files read at build time or run time? gaultier.github.io/blog/are_my_... #golang #dtrace

Go, SQL, and DTrace: a marriage made in heaven? New blog post! gaultier.github.io/blog/observe... #golang #dtrace #sql

Short article today! gaultier.github.io/blog/an_amus... #golang

The good thing about spending your Friday afternoon pulling your hair troubleshooting a bug, is that it makes for a nice blog article afterwards… gaultier.github.io/blog/subtle_... #bug #golang

I joined the Go team just after exploiting a carry bug in a Go assembly core, and I've been looking for ways to prevent the next one ever since. This year's attempt is very promising: mutation testing swapping e.g. ADC → ADD, CMOV → MOV, etc. to provide test coverage for constant time assembly.

Me: wow, my new work got me the new M4 MacBook Pro with 48 GB of RAM, every build is going to be instant! npm run build: Worker terminated due to reaching memory limit: JS heap out of memory. Tim Apple giveth, JavaScript taketh away

i hope to become the #1 RSS influencer

Modern webdev is so much. I'm installing so many packages and gems and I'm completely unsure of what is doing how and where. One day I'll have to get used to this stuff. It's very different from Systems Engineering.

Today I wanted to dtrace a nodejs application at work but then I discovered that nodejs removed dtrace support some time ago (static probes). Bummer. Still can do a lot just dtrace-ing system calls… but still, unfortunate. Reminds me of the talk “platform as a reflection of values…

... Well. I got a paper number, despite thinking I'd just hold onto it. No wording but I think it's about as complete as it can be. thephd.dev/_vendor/futu...

Me, after 10 years of coercing various crazy C & C++ build systems and mixed language codebases to work everywhere even on old unsupported BSDs: Unlimited power! I can do anything ! Me after 2 weeks of having to work with npm and the JavaScript world: I’m in danger.

Ever wondered if it’s possible to use DTrace on a Go program? Turns out it’s super easy, barely an inconvenience! gaultier.github.io/blog/an_opti... #golang #dtrace #optimization #debugging

Spent the last ~month trying to figure out why compiling my website took so long. Decided to turn it into a blog post :) sharnoff.io/blog/why-rus...

A subtle data race in Go: gaultier.github.io/blog/a_subtl... #golang #data-race

What should your mutexes be named? gaultier.github.io/blog/what_sh... #programming #golang #structural-search #awk

I recently had the honor of interviewing Zen’s chief architect Mike Clark! I tried to fit in as many microarchitecture questions as I could, including x64 vs ARM ISA power efficiency, 4k vs larger page sizes, 64-byte cache lines, scatter/gather and more: www.computerenhance.com/p/an-intervi...

New day, new blog article: gaultier.github.io/blog/build-p... #golang #pie #security

New blog article: gaultier.github.io/blog/tip_of_... #bpftrace #dtrace #golang #c

[1/2] The cloud, how it started vs how it's going. (based on a recent discussion with colleagues) 
#cloud #datacenter

New day, new blog article! Making my static blog generator 11 times faster: gaultier.github.io/blog/making_... #programming #git #optimization #odin

New week, new blog article: Making my debug build run 100x faster so that it is finally usable: gaultier.github.io/blog/making_... #programming #optimization #simd #c

New blog post: gaultier.github.io/blog/address... #golang #programming

New blog post: Tip of the day #4: Type annotations on Rust match patterns: gaultier.github.io/blog/tip_of_... The Rust compiler be like: coffee or tea? Wrong! It's tea.

New blog article: gaultier.github.io/blog/the_mis... #programming

Why Gelsinger was wrong for Intel bcantrill.dtrace.org/2024/12/08/w...