The GOTO Statement
summary
Narrative traces Dijkstra’s 1968 claim that the goto should be abolished and follows the decades‑long fight as C and C++ keep it while Java reserves it and removes it, cites the Apple goto fail SSL bug as a real‑world disaster caused by duplicate unconditional jumps, highlights ES6’s proper tail calls as a structured, efficient replacement enabling continuation‑passing and recursion without stack growth, and prescribes daily code reading like movie dailies to catch specification misunderstandings and bugs early.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:38Edsger Dijkstra the First Dutch Computer Programmer
- 8:12Progress Does Not Wait for the Next Idea It Waits for Consensus
- 10:28The Software Crisis
- 15:37Es6
- 16:52The Goto Fail Bug
- 23:02Recommend Code Reading
- 31:50What Happens if You Make a Language That Is Restricted Enough To Stop Stupid People from Making Terrible Mistakes
related talks
01h 01mSome Programming Myths Revisited
15mJava Devs Go! the Wrong Way 7 Times
01h 02mProcedural Programming: It Never Went Away
01h 08m“Declarative Control Flow"
01h 23mMidnote: Why Cpp Loops End
40mDay 3 Closing Talk: The Legacy of Go
01h 01mEasy to Use, Hard to Misuse: Declarative Style in C++
59m“The Exception Situation"