We Will All Be Game Programmers
summary
Argues that many web apps already borrow from games and demonstrates concrete techniques: uses game loop + requestAnimationFrame to keep simulations alive, a reproducible physics demo (Newton engine, version 500 of a stable box) that proves a time buffer yields identical runs across devices, and an update method pattern to decouple entities. Points out architectural parallels (Doom 3 scene builder vs React’s virtual DOM), shows a working HTML5 Minecraft‑like game with audio and upgrades, and says developers will adopt these patterns widely.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:05Heroku
- 3:45Why JavaScript
- 4:09Google Maps vs GTA
- 5:03Google Maps 2013
- 5:52Moon Patrol
- 7:39Interactive virtual environment
- 7:55Famous game engine
- 8:31Doom 3 architecture
- 9:43Its inevitable
- 10:02JavaScript
- 10:35PollyCraft
- 10:59Tooling Marketplace
- 11:19Game Dev Techniques
- 11:41Game Loop
- 16:43Dependency Injection
- 16:55Time Buffers
- 17:42Physics
- 18:04Time Buffer
- 19:28Newton
- 21:22Event Loop
- 22:48Outro
related talks
29mJavaScript and Game Development
34mThe past, present, and the future of HTML5 game development
29m"JavaScript as Play"
29mOnce Upon A Time, Somewhere Between Your Console And Browser
26mdeveloping videogames in JavaScript
31mMake coding fun: developing a game in the browser
54mThe Future of the Web-Apps
26mMaking games with JavaScript and Phaser.io