talk · HACKER NEWS RECOMMENDATION
Invited Talk - Guy Steele
ClojureTV · 7 HN recommenders · 8 recommendation months
Recommended by 7 Hacker News commenters across 8 months (2017–2023).
SignalTube analysis
Among 138 other talk videos tagged Programming language design, the mean is 3.1 distinct HN recommenders. This video has 7 distinct HN recommenders, about 2.2× that mean. Recommendations span 8 distinct months, longer than the peer average of 3.2 months. This is a data-derived comparison, not a human review or quality rating.
67% of its 12 labeled comments are marked as recommendations or strong recommendations. HN mention years are 2017–2023; those years describe discussion history, not upload date. Its verified runtime is 67 minutes 22 seconds. YouTube lists its publication date as 2017-10-13.
- Channel / speaker
- ClojureTV
- Verified runtime
- 1h 7m 22s
- YouTube upload date
- 2017-10-13
- Hacker News mention years
- 2017–2023
SAME TOPIC AND FORMAT
Compare with related videos
The comparison cohort uses other talk videos in Programming language design. “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 |
|---|---|---|---|---|---|---|
| Invited Talk - Guy SteeleCurrent video | 7 | 8 | 67% | — | 1h 7m 22s | 2017-10-13 |
| How Python was Shaped by leaky Internals, Armin Ronacher, Flask frameworktalk · Видео с мероприятий {speach! | 15 | 16 | 90% | No recorded overlap | 49m 55s | 2016-07-13 |
| Maybe Not - Rich Hickeytalk · ClojureTV | 14 | 11 | 70% | No recorded overlap | 63m 29s | 2018-11-30 |
| Why Isn't Functional Programming the Norm? – Richard Feldmantalk · Metosin | 12 | 12 | 70% | No recorded overlap | 46m 9s | 2019-09-30 |
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 contextual reference in “Strong typing, a hill I'm willing to die on”. Its short rationale: Steele notes type theorists use an untyped notation themselves.
The archive classifies this as a contextual reference in “How should I read type system notation?”. Its short rationale: Talk on the ambiguous, unspecified notation used across computer science.
The archive classifies this as a recommendation in “How should I read type system notation?”. Its short rationale: Names and explains type-system notation like inference rule diagrams.