Top all-time · #3671
David Lattimore
Personal blog · davidlattimore.github.ioprogrammingsystems
David Lattimore's personal blog at davidlattimore.github.io covers programming and systems. Since 2023, 21 different Hacker News readers have linked it 31 times, most often “Wild performance tricks”. It is still writing: the last post was on 2026-09-18, and you can follow it by feed.
Too few sampled comments (8) to say how often HN recommends it.?
Why HN links it
HN readers link David Lattimore's blog for posts on Rust performance and compile-time work, including the wild linker, and for a supply-chain attack explainer tied to the Cackle tool.
Summarised by Claude from a sample of 8 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Wild performance tricks5 people · 6 mentions · first linked 2025-09-03
- Making Rust supply chain attacks harder with Cackle4 people · 4 mentions · first linked 2023-10-11
- Speeding up rustc by being lazy3 people · 3 mentions · first linked 2024-06-06
- Benchmarking Wild vs. Mold3 people · 3 mentions · first linked 2026-09-18
- Rust Dylib Rabbit Holes2 people · 2 mentions · first linked 2024-08-28
- Wild Linker Update – 0.6.02 people · 2 mentions · first linked 2025-09-23
- Graph Algorithms in Rayon2 people · 2 mentions · first linked 2025-11-27
- Designing Wild's Incremental Linking2 people · 2 mentions · first linked 2024-12-03
- /2 people · 2 mentions · first linked 2024-11-15
What Hacker News says?
I went looking for some writing by the author about how he made wild fast, but couldn't find much: https://davidlattimore.github.io/
Comment linking /
on “Wild – A fast linker for Linux”Submitted Wild performance tricks as a story · 138 points
HN discussionRust supports dynamic linking btw. https://robert.kra.hn/posts/2022-09-09-speeding-up-increment... https://davidlattimore.github.io/posts/2024/08/27/rust-dylib...
Comment linking /posts/2024/08/27/rust-dylib-rabbit-holes.html
on “AnduinOS”Submitted Speeding up the Rust edit-build-run cycle as a story · 113 points
HN discussionLooks like he's been continuing to work on it. GitHub repo: https://github.com/davidlattimore/wild List of his blog posts, a couple of which are about wild: https://davidlattimore.github.io/
Comment linking /
on “Speeding up the Rust edit-build-run cycle”Submitted Rust Dylib Rabbit Holes as a story · 63 points
HN discussionusually with Rust impactful savings come from writing the Rust differently, not from doing hand-written assembly instead. See stuff like https://davidlattimore.github.io/posts/2025/09/02/rustforge-... This doesn't mean Rust is near perfect, it's just that your first move should be "how do I make the Rust better" and not "I need to drop into asm."
Comment linking /posts/2025/09/02/rustforge-wild-performance-tricks.html
on “Beating the compiler (2024)”Submitted Benchmarking Wild vs. Mold as a story · 47 points
HN discussionIdk. Did you see the "Buffer reuse" section of this blog post? [1] Kudos to that guy for solving the puzzle, but I really don't want to use a special trick to get the compiler to let me reuse a buffer in a for loop. [1]: https://davidlattimore.github.io/posts/2025/09/02/rustforge-...
Comment linking /posts/2025/09/02/rustforge-wild-performance-tricks.html
on “Any application that can be written in a system language, eventually will be”Submitted Wild Linker Update – 0.6.0 as a story · 8 points
HN discussion> Want it fast? Turn off the runtime checks by calling unsafe code. You can do that for sure, but you can also sometimes write your code in a different way. https://davidlattimore.github.io/posts/2025/09/02/rustforge-... is an interesting collection of these. > it doesn't read like the author has spent weeks in a profiler combing over machine code to optimize Rust code It is true that this blog post was not intended…
Comment linking /posts/2025/09/02/rustforge-wild-performance-tricks.html
on “Is Rust faster than C?”Submitted Wild Performance Tricks in Rust as a story · 7 points
HN discussionI recently saw a post about Cackle [1] coming out of the rust ecosystem which looks pretty cool. Similar to what others have said, there's always a chance that a C lib or shell script is leveraged to bypass compile time guarantees. I think that's why it's important to do both. Do what you can to keep your supply chain safe and limit your runtime as much as possible. [1] https://davidlattimore.github.io/making-supply…
Comment linking /making-supply-chain-attacks-harder.html
on “Porting Linux Pledge to Go”Submitted Wild Performance Tricks – David Lattimore as a story · 6 points
HN discussionI found this hypothetical story to explain a supply chain attack easy to understand: https://davidlattimore.github.io/making-supply-chain-attacks...
Comment linking /making-supply-chain-attacks-harder.html
on “Making Rust supply chain attacks harder with Cackle”Submitted Benchmarking Wild vs. Mold as a story · 4 points
HN discussionSubmitted Benchmarking Wild vs. Mold as a story · 4 points
HN discussionSubmitted Graph Algorithms in Rayon as a story · 4 points
HN discussionSubmitted Designing Wild's Incremental Linking as a story · 3 points
HN discussionSubmitted Speeding up rustc by being lazy as a story · 3 points
HN discussionSubmitted Wild Linker Update – 0.9.0 as a story · 2 points
HN discussionSubmitted Wild Linker Update – 0.6.0 as a story · 2 points
HN discussionSubmitted Testing a Linker as a story · 2 points
HN discussionSubmitted Speeding up rustc by being lazy as a story · 2 points
HN discussionSubmitted Speeding up rustc by being lazy as a story · 2 points
HN discussionSubmitted Speeding up Rust edit-build-run cycle as a story · 2 points
HN discussionSubmitted Making Rust supply chain attacks harder with Cackle as a story · 2 points
HN discussionSubmitted Graph Algorithms in Rayon as a story · 1 points
HN discussionSubmitted Designing Wild's Incremental Linking as a story · 1 points
HN discussionSubmitted Making Rust supply chain attacks harder with Cackle as a story · 1 points
HN discussion
