talk · HACKER NEWS RECOMMENDATION
Rust NYC: Jon Gjengset - Demystifying unsafe code
Rust Programming Language · 2 HN recommenders · 2 recommendation months
Recommended by 2 Hacker News commenters across 2 months (2020–2024).
SignalTube analysis
Among 132 other talk videos tagged C, C++, Rust, Go & systems languages, the mean is 3.1 distinct HN recommenders. This video has 2 distinct HN recommenders, below that mean. Recommendations span 2 distinct months; the peer average is 3.2 months. This is a data-derived comparison, not a human review or quality rating.
67% of its 3 labeled comments are marked as recommendations or strong recommendations. HN mention years are 2020–2024; those years describe discussion history, not upload date. Its verified runtime is 29 minutes 25 seconds. YouTube lists its publication date as 2020-03-10.
- Channel / speaker
- Rust Programming Language
- Verified runtime
- 29m 25s
- YouTube upload date
- 2020-03-10
- Hacker News mention years
- 2020–2024
SAME TOPIC AND FORMAT
Compare with related videos
The comparison cohort uses other talk videos in C, C++, Rust, Go & systems languages. “Shared recommenders” counts HN users who recommended both videos in the source graph.
| Video | HN recommenders | Recommendation months | Positive label share | Shared recommenders | Runtime | Upload date |
|---|---|---|---|---|---|---|
| Rust NYC: Jon Gjengset - Demystifying unsafe codeCurrent video | 2 | 2 | 67% | — | 29m 25s | 2020-03-10 |
| Lexical Scanning in Go - Rob Piketalk · GoogleFOSSSydney | 13 | 12 | 65% | No recorded overlap | 51m 18s | 2011-08-30 |
| CppCon 2016: Jason Turner “Rich Code for Tiny Computers: A Simple Commodore 64 Game in C++17”talk · CppCon | 13 | 10 | 65% | No recorded overlap | 79m 52s | 2016-09-24 |
| CppCon 2017: Matt Kulukundis “Designing a Fast, Efficient, Cache-friendly Hash Table, Step by Step”talk · CppCon | 9 | 10 | 53% | No recorded overlap | 59m 34s | 2017-10-26 |
THREE SOURCE-BASED CONTEXT POINTS
Why Hacker News recommends it
Each note combines the dataset’s stance label and short rationale; comment bodies are not reproduced. Open the HN source for the original discussion.
The archive classifies this as a recommendation in “Compiling C to Safe Rust, Formalized”. Its short rationale: Talk by a trusted expert on unsafe Rust difficulty.
The archive classifies this as a contextual reference in “The Rustonomicon”. Its short rationale: Gjengset argues unsafe is a mystery, not inherently evil.
The archive classifies this as a recommendation in “How to speed up the Rust compiler in 2020”. Its short rationale: Talk demystifying unsafe Rust.