complicit in the whole thing. Why I sat on this for a few days And before we take a look at the full timeline and where we're at, let me take a moment to explain myself: I've been on both sides of internet mobs before. I've been the canceller, the cancellee (boy did I fuck up, several times), and I've had my site DDoS'd for the lulz. I've been the

compressed-debug $ objcopy --strip-all ./target/debug/pdftocairo /tmp/pdftocairo.stripped $ ls -lhA /tmp/pdftocairo.stripped -rwxr-xr-x. 1 amos amos 5.3M Nov 25 13:04 /tmp/pdftocairo.stripped During my tenure as "chief fucking around and finding out officer", I've built software from sources "manually" a ton. If you somehow need to get good at

xor rdi,rdi 0040101E B83C000000 mov eax,0x3c 00401023 0F05 syscall Executing "samples/hello" in memory... code @ 0x561828e69000 entry offset @ 00000000 entry point @ 0x561828e69000 Fuck. I'm pretty sure hello was supposed to print something. $ ./samples/hello hi there Yes, yes, it was. What the heck is happening

could even get gir to generate those! If only someone... contributed that feature upstream... Oh no no no not ag- Looking into gtk-rs/gir...fuck's sake. So the first wrinkle is that, at the time of this writing, there's gir 0.14, and gir's default branch, adn they generate incompatible code. So we'll need to regenerate all crates. Weren't we

solo just so your blog slash video platform is juuuuust the way you like it. So instead of buying a fuck-you CPU (like a Threadripper, or something more consumery like the latest Ryzens), maybe you rent a big cloud machine that you can turn on and off as needed. Just for the big stuff. If you need a bunch of CPU to work directly on the Rust project

increment(); } false => { println!("wasn't even"); } } dbg!(&s.lock()); } $ cargo run --quiet ^C Huh. HUH! Huh. That one... does not spark joy. What the fuck is happening?...is a fair question, considering. See, the thing with match is, it lets you do pattern matching. As opposed to if, which just does

interpreter /lib/ld64.so.1, not stripped $ ./hello-pie zsh: no such file or directory: ./hello-pie WHAT? That's it. I give up. I quit. Thanks for the support everyone, but I can't take this anymore. Nothing makes sense, up is down, files exist and are executables but they won't execute, fuck all this, I'm out.Cool bear's hot tip Hey what's that

Rust. Sure. Well, no, not that part, but for example.. Oh yeah, sure, in debug builds Rust will check that when you add up two random numbers you've read from fuck-knows-where in a poor ELF file, they don't underflow an u64. Oh yeah. Well done. Bravo. Super safe. But- Admit it. You just don't have what it takes to write in assembly. You're a little

assertion failing is:// (in tokio code, in `src/time/driver/entry.rs`) debug_assert!(cur_state < STATE_MIN_VALUE); Huh, a debug_assert!. That means that in production... $ RUST_BACKTRACE=1 cargo run --quiet --release (program never outputs anything, never exits either) Hah. I guess they're not fucking around about the "undefined

is still a warning - just something we should look at when we get a chance, but not a showstopper. (Unless we slap #![deny(unreachable_code)] at the start of our main.rs, the equivalent of passing -Werror=something to gcc/clang). Fuck around now, find out... when? Let's change our sample a little bit. Say we remove the definition of bar entirely