HN repeatedly recommends it as a master class in limited-palette pixel art and palette cycling, from an artist behind Loom and Monkey Island.
Topics › Games & Game Development
The best game history & retro gaming videos, according to Hacker News
104 videos about game history & retro gaming that Hacker News commenters keep pointing each other to, ranked by how many separate months they were recommended. Part of Games & Game Development.
Praised as a brilliant, deadpan and inventive hardware hack, and a good starting point for Tom7's videos.
HN treats it as the standard starting point for Game Boy emulator writers and homebrew developers, with several calling it one of their favorite talks.
It is one of the most frequently recommended videos on HN for old-school game development hacks under tight hardware constraints.
Frequently recommended as an entertaining account of a failed launch and recovery, especially in threads about Star Citizen and over-promising.
Loved on HN as a hilarious, brilliant example of hacker-academic work and cited whenever game-playing AI or fuzzing comes up.
Constantly cited as the canonical example of arbitrary code execution through gameplay and of deep system knowledge among speedrunners.
Frequently recommended whenever Diablo or its origins come up, for its candid account of the human side of game development.
HN loves the deep, hands-on look at N64 hardware quirks such as bus contention and the surprisingly large wins from low-hanging optimizations.
HN points to it whenever discussion turns to how old games were so small, as a clear tour of 8-bit optimization and creative work under hardware limits.
HN points people to it as a deep dive showing how complex logic was built without computers.
HN recommends it as a great account of how Civilization was made and as a source on perceived fairness in game design.
Repeatedly recommended as a favorite tech talk and a great example of digital preservation work.
HN recommends it as a transparent MMO postmortem and as the source of the story that the term 'shard' originated with Ultima Online.
It is the go-to explanation of why games that die when servers shut down harm consumers, and it is repeatedly cited in Stop Killing Games and game-delisting threads.
HN shares it whenever Zork or text adventures come up, as a fun tribute for geeks.
HN recommends it to anyone interested in text adventures, Infocom, MUDs and early computer gaming history.
Recommended as a well-researched piece of computing history on Amiga FPS games and Doom's impact.
HN treats it as required viewing for understanding the PS5's SSD and architecture beyond raw specs.
Repeatedly called essential viewing for game development history and clever work under memory constraints.
HN commenters point to it as the first-person story of how Myst grew out of HyperCard and fit on CD-ROM, especially in threads about HyperCard and retro game constraints.
Recommended as a fascinating look at fitting a modern game into NES constraints.
HN cites it for the story of how Pitfall's levels are generated procedurally from a seeded counter, within 4K of ROM.
HN points to it as the standard demonstration of arbitrary code execution on a Game Boy, and of glitches and bugs being turned into a working computer.
HN plugs it as a favorite example of what skilled demoscene coders can pull out of 30-year-old hardware.
Recommended whenever Atari vector games come up as an excellent, deep technical explanation of how they worked.
HN recommends it as the thorough, well-researched answer to the first video game question.
Recommended as a well-made documentary-style history that gives context around the game and inspires replays.
HN uses it as a canonical anecdote that designers badly predicted player behavior, and in threads about UO and sharding.
Recommended as a well-researched rebuttal of the idea that Nintendo simply forgot an optimization flag.
HN recommends it as a gripping entry point into speedrunning and as a model of a well-made history video.
HN recommends it as an excellent inside look at Valve's history, its technology and the games industry of the time.
HN fans share it as a way to hear the game's philosophical, sci-fi quotes in sequence.
Cited as a source for Carmack's views on static analysis, open source and languages, and praised as a captivating, conversational speaker.
Held up as an exemplary GDC postmortem and a first-hand account for fans of the original Fallout.
HN recommends it as an entertaining deep dive on CRT versus LCD rendering of retro games and the case for CRT shaders.
Recommended as an inspiring story of hardware reverse engineering and persistence.
HN recommends it as a fascinating engineering story of early console online play, including a working demo.
HN recommends it as an approachable explanation that makes the famous algorithm finally make sense.
Cited as a landmark of speedrunning, where a trick once limited to tool-assisted runs was pulled off live on hardware.
HN recommends it as a rigorous, fun example of reverse engineering a game to predict and conquer its RNG.
HN points to it whenever Another World comes up, as one of the better GDC talks by the game's creator.
HN considers it one of the best GDC post-mortems, with funny anecdotes (such as turning down Hotmail equity) and multiplayer insights.
Recommended as a clear, approachable explanation of how retro graphics hardware actually worked.
HN rates it among the best gaming video essays and Ahoy as one of the best creators on the platform.
HN recommends it as an excellent documentary on Tetris and its tangled licensing history.
HN commenters recommend it as a firsthand account from the creator, including the old tooling.
Fans of Transport Tycoon and OpenTTD point to it as a nostalgic, live-instrument version of the game's music.
HN points to it as the original statement of the Stop Killing Games campaign.
Recommended as a deep-dive rabbit hole showing extraordinary knowledge of game internals.
HN commenters recommend it as a showcase of the deep reverse-engineering and glitch knowledge behind speedrunning, and cite it for the wrongwarp trick.
HN points to it as a stunning demonstration of arbitrary code execution in a console game and of what speedrunners effectively do as vulnerability researchers.
HN commenters recommend it as a showcase of remarkable sight-reading and a favorite when sight-reading or notation comes up.
HN commenters recommend it as an amazing overview of the technical feats and history behind Elite, and cite it for what the 6502 could do.
HN recommends it as a fascinating hacker war story, especially in threads on Naughty Dog's custom Lisp languages GOOL and GOAL.
HN points to it as a clear, lawyer-made summary during Nintendo emulator disputes like Yuzu.
Recommended as a clear overview of Another World's graphics and programming and what the Amiga could do.
Linked in Spacewar and vintage computing threads as a charming demo on real hardware.
HN points to it as the clearest short demo of iMUSE, considered a high point in video game music.
HN commenters recall it as a mind-blowing early 3D game that showed what the Archimedes hardware could do.
Cited in anti-piracy discussions as a clear explanation of clever retro copy-protection tricks, though one commenter disputes a claim about Leander.
HN commenters recommend it as an accessible, non-technical look at real game pathfinding problems from a developer who built them.
Pointed to as an impressive technical N64 homebrew demo showing unexpectedly high-res textures.
HN commenters point to it as a fantastic developer commentary on how Doom's first episode was made.
Shared as a favorite game-development anecdote with a clear technical explanation.
HN points to it as coverage of an impressive 3D game port on very limited hardware.
HN points to it as a good documentary on GOG's history and the difficulty of tracking down rights holders.
HN recommends it as a thorough, well-researched history, and one commenter finds such videos more exhaustive than Wikipedia's sourced articles.
Recommended as the best video account of the Hareraiser affair when treasure-hunt and puzzle stories come up.
Cited as the go-to demonstration of how hard and clever Atari 2600 graphics programming was.
HN recommends it as a detailed RCT documentary in threads on the game's optimization and design legacy.
HN people cite it as the clearest explanation of how the credits warp exploit works.
Cited in discussions of sine implementations and whether lookup tables beat computation on memory-bound hardware.
HN recommends it for first-hand accounts of how early 3D games like Doom worked within tight hardware limits.
Strongly recommended as an inspiring hour on how id worked, often linked in programming-practice threads.
Recommended as a compact account of the Atari-Nintendo lawsuit and its technical and legal details, which shaped the game industry.
Quoted in privacy and surveillance debates, and praised as some of the best science fiction writing in games.
Used as a nostalgic link to a beloved childhood game, and as an example of a tight failure-iteration learning loop.
HN people recommend it as the best overview of how 3D on the GBA progressed over the console's life, usually in threads about GBA ports and homebrew 3D engines.
HN people mention it as a notable historical talk from the early game industry, though some see it as showing his eccentricity.
HN recommends it as an in-depth look at mechanical logic, and uses it as an analogy for state machines and biological instruction processing.
HN uses it to show a classic early Mac game, noting its low-latency input and early audio showcase.
HN mentions it for the game design history it contains and as part of a list of good gaming history channels.
Cited as an example of a compact, ready-made way to play retro DOS games on real hardware without collecting old machines.
HN uses it as a showcase of extreme FPS movement skill, such as rocket and grenade jumping.
HN cites it as the standard walkthrough of Mario's implicit teaching and as an example of hiding the tutorial inside the problem.
HN points to it as the concise explanation of the latest competitive NES Tetris technique.
HN points to it as investigative journalism backing the view that vintage game prices are inflated by wash trading and grading services.
HN cites it as the example showing why CRT emulation is needed to render effects the original artists intended.
HN uses it to show what the Nintendo PlayStation prototype hardware actually looked like, essentially an SNES with a CD-ROM drive.
Used as the accessible explanation of PS1 rendering quirks whenever retro 3D graphics or PS1-style renderers come up.
HN shares it for nostalgia about the tinny PC speaker sound of early adventure games.
Cited as footage of a famous piece of gaming history whenever id Software, Commander Keen, or scrolling tech comes up.
Cited as a historical reference that Halo was first announced at Macworld, with Steve Jobs involved, and nearly launched as a Mac game.
Cited as shorthand for one of the most effective moments in console marketing and for how a price announcement can sink a rival.
HN links it as a historical artifact showing what Minecraft looked like at its very beginning.
Shown as a historic example of fractal terrain rendering in games, in threads about voxel and terrain rendering.
Cited mostly as a retro-tech curiosity about Microsoft's push into PC gaming, and sometimes as a joke.
Pointed to as a walkthrough of the BASIC listing of a famous game partly written in BASIC.
Cited as the canonical example of Quake running on an exotic display, usually in 'will it run Doom' threads.
Pointed to as a rare look at the real SCUMM code of a classic adventure game.
Used as the canonical example of arbitrary code execution through nothing but controller input, often in talks about speedrunning and exploits.
HN references it as a demonstration of Doom's original multi-monitor support and as retro computing content.
Quoted as a nostalgic joke about DOS-era game setup.
Which of these have you already seen?
Connect YouTube and HackerTube AI hides what you've watched and ranks the rest for you.