talk · HACKER NEWS RECOMMENDATION
CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon · 7 HN recommenders · 11 recommendation months
Recommended by 7 Hacker News commenters across 11 months (2017–2025).
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 7 distinct HN recommenders, about 2.3× that mean. Recommendations span 11 distinct months, longer than the peer average of 3.1 months. This is a data-derived comparison, not a human review or quality rating.
69% of its 16 labeled comments are marked as recommendations or strong recommendations. HN mention years are 2017–2025; those years describe discussion history, not upload date. Its verified runtime is 72 minutes 27 seconds. YouTube lists its publication date as 2015-10-13.
- Channel / speaker
- CppCon
- Verified runtime
- 1h 12m 27s
- YouTube upload date
- 2015-10-13
- Hacker News mention years
- 2017–2025
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 |
|---|---|---|---|---|---|---|
| CppCon 2015: Andrei Alexandrescu “std::allocator...”Current video | 7 | 11 | 69% | — | 1h 12m 27s | 2015-10-13 |
| 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 joke in “I was surprised by how simple an allocator is”. Its short rationale: the source snapshot has no short rationale for this mention.
The archive classifies this as a strong recommendation in “Comptime as Configuration”. Its short rationale: Composing a complex allocator from trivial parts at compile time.
The archive classifies this as a contextual reference in “Please do not attempt to simplify this code”. Its short rationale: the source snapshot has no short rationale for this mention.