Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #6668

B

bheisler.github.io

Personal blog · bheisler.github.io/postprogrammingsystems

bheisler.github.io is a personal blog at bheisler.github.io about programming and systems. Since 2017, 11 different Hacker News readers have linked it 13 times, most often “Experiments in NES JIT Compilation”. The last post was in 2021, but the archive is still widely read.

Visit the blog
13mentions?
11HN people?
2017–2024first – last linked?
Links on Hacker News per year · peak 6 in 2017

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

Linked for posts on running Rust code on the GPU, such as GPU-accelerated path tracing and compiling Rust for GPUs. Commenters also cite the author's Criterion benchmarking library.

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?

  1. Experiments in NES JIT Compilation
    2 people · 2 mentions · first linked 2017-08-21
  2. Parsing NES ROM Headers with Nom
    2 people · 2 mentions · first linked 2017-07-30

What Hacker News says?

  1. Criterion is still the gold standard. Pros for Criterion over the stdlib: https://github.com/bheisler/criterion.rs#features Downsides of Criterion: https://bheisler.github.io/criterion.rs/book/user_guide/know...

    Comment linking /criterion.rs/book/user_guide/known_limitations.html

    on “How Rust 1.64 became faster on Windows”
  2. Submitted Writing a Raytracer in Rust – Part 1 as a story · 177 points

    HN discussion
  3. drran · 2020-04-19Recommends
    You may want to look at this article for further inspiration: https://bheisler.github.io/post/writing-gpu-accelerated-path...

    Comment linking /post/writing-gpu-accelerated-path-tracer-part-3/

    on “Show HN: Monte Carlo ray tracer in Rust”
  4. Submitted Experiments in NES JIT Compilation as a story · 71 points

    HN discussion
  5. Sort of; it's not trivial, but some people have done it. See https://bheisler.github.io/post/rust-on-the-gpu-with-accel/ for example. I think https://blog.theincredibleholk.org/blog/2012/12/05/compiling... is the earliest one I know of; two and a half years before Rust 1.0!

    Comment linking /post/rust-on-the-gpu-with-accel/

    on “Graphics Team ships WebRender MVP”
  6. Submitted Parsing NES ROM Headers with Nom as a story · 3 points

    HN discussion
  7. If you want to "go low" in the operating system, you could write a Linux kernel module: https://sysprog21.github.io/lkmpg/ https://blog.sourcerer.io/writing-a-simple-linux-kernel-modu... If you want to "go low" in the way hardware works, you could try and write an interrupt handler on an embedded device. If you want to "go low" in how optimizations work in application development, you could try and implement microbe…

    Comment linking /criterion.rs/book/index.html

    on “Ask HN: Going low-level – what to learn next?”
  8. Submitted Calling Rust from Python as a story · 2 points

    HN discussion
  9. Submitted Parsing NES ROM Headers with Nom and Rust as a story · 2 points

    HN discussion
  10. Submitted Criterion.rs v0.3.4 and Iai 0.1.0 as a story · 1 points

    HN discussion
  11. Submitted Building a Recipe Manager – Part 5 – Data Integrity as a story · 1 points

    HN discussion
  12. Submitted Building a Recipe Manager – Part 2 – Druid Experience Report as a story · 1 points

    HN discussion
  13. Submitted Experiments in NES JIT Compilation in Rust as a story · 1 points

    HN discussion

Search all of HN for bheisler.github.io

Linked by the same people?