Privacy Policy
👋 This page was last updated ~3 years ago. Just so you know.
Analytics are measured with Umami, a privacy-respecting solution.
Visting a website means your IP address is sent to several systems. We make no effort to retain it anywhere.
Donors (see Terms and Conditions) have their Patreon/GitHub display name appear in the “thanks” section of some articles, unless they opt out of it (only GitHub lets you mark a donation as “private”).
Cancelling donation makes the name disappear (automatically) from those credits.
You can e-mail [email protected] if you have questions.
Did you know I also make videos? Check them out on PeerTube and also YouTube!
Here's another article just for you:
A dynamic linker murder mystery
I write a ton of articles about rust. And in those articles, the main focus is about writing Rust code that compiles. Once it compiles, well, we’re basically in the clear! Especially if it compiles to a single executable, that’s made up entirely of Rust code.
That works great for short tutorials, or one-off explorations.
Unfortunately, “in the real world”, our code often has to share the stage with other code. And Rust is great at that. Compiling Go code to a static library, for example, is relatively finnicky. It insists on being built with GCC (and no other compiler), and linked with GNU ld (and no other linker).