Top all-time · #20238
Kibeom Kim
Personal blog · kkimdev.github.io/posts · on HN as kkimdevprogrammingsystems
Kibeom Kim's personal blog at kkimdev.github.io covers programming and systems. Since 2018, 3 different Hacker News readers have linked it 3 times, most often “Rust – Compile Time Memory Safety”. The last post was in 2018, but the archive is still widely read.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
Kibeom Kim's posts explain how Rust's compile-time checks enforce memory safety, and HN readers cite them when discussing unsafe code. The one comment links the post as support for its own point.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Rust – Compile Time Memory Safety2 people · 2 mentions · first linked 2019-04-23
What Hacker News says?
> Rust does not compile if you don't use the techniques you described? Yes, exactly. https://kkimdev.github.io/posts/2019/04/22/Rust-Compile-Time... Of course, you can bypass this by using 'unsafe' code, where you are explicitly telling the compiler that you have manually verified Rust's safety guarantees. This is why a significant portion of Rust's community gets agitated with (possibly unnecessary) use of 'unsafe'…
Comment linking /posts/2019/04/22/Rust-Compile-Time-Memory-Safety.html
on “Chromium project finds that 70% of security defects are memory safety problems”Submitted Rust – Compile Time Memory Safety as a story · 175 points
HN discussionSubmitted IEEE 754 Floating Point Type in C++ as a story · 65 points
HN discussion