HackerTubewatch
Surprise me
Frame from Turing & The Halting Problem - Computerphile Plays via YouTube's privacy-enhanced embed

Turing & The Halting Problem - Computerphile

21 videos recommended on HN
YouTube
2 HN users recommended this explainer2 months2019–2022 score 2
Years with an HN recommendation, 2007–2026

Offered as a short, clear explanation of the halting problem and its link to decidability.

A Computerphile video in which Mark Jago of the University of Nottingham explains Turing's halting problem and how it led to the blueprint for the modern computer.

“Here's a short video on it” (HN, 2021)

2 recommendations · 2 citations · Explainers · intro

4 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@mar77i Dec 2019 Recommends
on HN thread Kurt Gödel and the Mechanization of Mathematics
For one practical example, Gödel's incompleteness is directly related to decidability problems in CS. there's this glorious liar paradox machine discussed by Computerphile [0]. [0] [this video]
Liar paradox machine illustrating link between incompleteness and decidability

Citations, criticism and jokes

@cartoonworld Jul 2021 Cites it
on HN thread Up to 1,500 businesses affected by ransomware attack, Kaseya CEO says
Read more
In my view, this isn't really a software problem. Your plan is on the right track though. We already know its neigh impossible to ensure software is bug and vuln free. We have to reckon with the fact that secure software is possible, but extremely hard and impractical to achieve with any regularity. Because of well known computer science problems such as the Halting Problem[0] and more that I am totally ignorant of, the only alternative is extremely thorough verification like happens in planes[1]. The rub is that unlike aerospace and other critical controls, we cannot define the software security problem as closely as is possible in those other critical systems. Doing so will undo the benefits of our general technology solutions. The reason I claim it is nonetheless not a software problem is: In case after case of these troubling examples of security failures, there are only a few organizational commonalities that link them all together. Time after time, there are shocking misconfigurations, corners cut, best practices eschewed, warnings ignored, processes disregarded or absent and swept under the rug. C-Suite execs, as has been well noted, opt for the checkbox-style silver-bullet-whiz-bang, because they can understand the value proposition of one-problem-one-fix and it is easy to communicate to stakeholders. They are totally ignorant to and uninterested in the details of actually providing a quality product. Their product is often not what they are selling; They are getting
@verdverm Aug 2022 Cites it
on HN thread Tornado Cash and collateral damage
no, it's all in software because you can create any smart contract and it can call any other. There is a difference in knowing after the transaction has finalized and predicting beforehand, which is when you would want to block the transaction. [this video]

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close