@pgaultier.bsky.social

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.

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

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.

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

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…