Top all-time · #13699
Code Slow
Personal blog · codeslow.comprogramminggames
Code Slow is a personal blog at codeslow.com about programming and games. Since 2020, 5 different Hacker News readers have linked it 5 times, most often “Writing a winning 4K intro in Rust”. The last post was in 2021, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for posts on shrinking Rust binaries and on writing 4k intros in Rust. Commenters cite it when discussing binary size and memory safety in low-level languages.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /2019/12/tiny-windows-executable-in-rust.html2 people · 2 mentions · first linked 2020-08-20
- Writing a winning 4K intro in Rust2 people · 2 mentions · first linked 2020-07-05
What Hacker News says?
Another post for size constraint coding in Rust: https://www.codeslow.com/2020/01/writing-4k-intro-in-rust.ht...
Comment linking /2020/01/writing-4k-intro-in-rust.html
on “Minimizing Rust Binary Size”Submitted Writing a winning 4K intro in Rust as a story · 330 points
HN discussionThat post is, but https://www.codeslow.com/2020/07/writing-winning-4k-intro-in... is a 4k demo. And yes, a lot of it is unsafe, because it's calling into all of that stuff directly, and doing pointer arithmetic, etc. Check the post, it's good, the Conclusion section talks about this specifically.
Comment linking /2020/07/writing-winning-4k-intro-in-rust.html
on “Porting a Golang and Rust CLI tool to D”Rust is statically linked by default, not sure how D works. Rust still includes some debug features that can give you a stack trace. Size will also depend on the compile options, if LTO was enabled, how much generics were used, how much string printing was used (print is a macro in Rust that generates code at the callsite), etc. Most, if not all, of these can be resolved. See https://github.com/johnthagen/min-sized-…
Comment linking /2019/12/tiny-windows-executable-in-rust.html
on “Porting a Golang and Rust CLI tool to D”It's a bit unfair to use a default hello world program as an argument for why binaries are too large to use in an embedded context, because rust binaries can be made very small with tuning[1][2][3]. [1] https://www.codeslow.com/2019/12/tiny-windows-executable-in-... [2] https://github.com/johnthagen/min-sized-rust [3] https://rust-embedded.github.io/book/unsorted/speed-vs-size....
Comment linking /2019/12/tiny-windows-executable-in-rust.html
on “Inline and Sideline Approaches for Low-Cost Memory Safety in C”