HackerTubeHN

talk · HACKER NEWS RECOMMENDATION

Ron Pressler - Pull Push: Please stop polluting our imperative languages with pure concepts-Curry On

Curry On! · 3 HN recommenders · 4 recommendation months

YouTube

Recommended by 3 Hacker News commenters across 4 months (2015–2024).

SignalTube analysis

Among 138 other talk videos tagged Programming language design, the mean is 3.2 distinct HN recommenders. This video has 3 distinct HN recommenders, close to that mean. Recommendations span 4 distinct months; the peer average is 3.2 months. This is a data-derived comparison, not a human review or quality rating.

100% of its 4 labeled comments are marked as recommendations or strong recommendations. HN mention years are 2015–2024; those years describe discussion history, not upload date. A verified runtime is not present in the current metadata snapshot. A verified YouTube publication date is not present in the current metadata snapshot.

Channel / speaker
Curry On!
Verified runtime
Not verified in the current YouTube metadata
YouTube upload date
Not verified
Hacker News mention years
2015–2024

SAME TOPIC AND FORMAT

Compare with related videos

138 peers

The comparison cohort uses other talk videos in Programming language design. “Shared recommenders” counts HN users who recommended both videos in the source graph.

VideoHN recommendersRecommendation monthsPositive label shareShared recommendersRuntimeUpload date
Ron Pressler - Pull Push: Please stop polluting our imperative languages with pure concepts-Curry OnCurrent video34100%—Not verified in the current YouTube metadataNot verified
How Python was Shaped by leaky Internals, Armin Ronacher, Flask frameworktalk · Видео с мероприятий {speach!151690%No recorded overlapNot verifiedNot verified
Maybe Not - Rich Hickeytalk · ClojureTV141170%No recorded overlapNot verifiedNot verified
Why Isn't Functional Programming the Norm? – Richard Feldmantalk · Metosin121270%No recorded overlapNot verifiedNot verified

THREE SOURCE-BASED CONTEXT POINTS

Why Hacker News recommends it

4 mentions

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 “Async await: the worst thing to happen to programming?”. Its short rationale: Arguments against async/await from virtual threads advocate.

The archive classifies this as a recommendation in “Java Virtual Threads: A Case Study”. Its short rationale: Case for simple blocking code over non-blocking IO styles.

The archive classifies this as a recommendation in “Go proposal: Leave “if err != nil” alone?”. Its short rationale: Talk on not over-relying on mathematical purity for correctness.