Do You Want to Play Doom in Your Browser?

on YouTube ↗23m

" summary

Claims that original Doom C source is compiled to run in the browser using Emscripten + WebAssembly, shows a GitHub fork that required nontrivial fixes, and documents asset memory limits (64‑bit extensions toward 4 gigabits that still constrain modern ports. Concrete tools include Chocolate Doom compiled via Emscripten, inscrip/asmjs troubleshooting, and a live demo that earlier succeeded but proves brittle and fails during the session; a cited figure says 98% of players favor older games.

AI-written summary · about

" chapters (9)

1. 0:00Introduction to speaker
2. 2:27Evolution of web gaming
3. 3:59The rise of WebAssembly
4. 5:01Wasm in modern applications
5. 6:43Gaming milestones on the web
6. 11:04Running Doom in the browser
7. 12:52Market trends in web gaming
8. 15:43Technical demo and challenges
9. 19:23Closing and Q&A

" related talks

• 01h 09mSandbox Games: Using WebAssembly and C++ to make a simple gameÓlafur Waage · Meeting C++ 2022
• 01h 12mSandbox Games - Using WebAssembly and C++ to Make a Simple GameÓlafur Waage · ACCU 2022
• 32mJavaScript is the new metal the cloud vs the browserScott Hanselman · ngAtlanta Conf 2018
• 46mOne Pixel Then Another: How to Run DOOM on an E‑ReaderMoustapha Agack · DevFest Toulouse 2025
• 59mEmscripten and asm.js: C++'s role in the modern webAlon Zakai · CppCon 2014
• 31mThe CPU in your browser: WebAssembly demystifiedAntonio Cuni · PyCon US 2023
• 27mFast future with WebAssemblyMilica Mihajlija · VinnytsiaJS 2019
• 34mModern Web Game DevelopmentTom Greenaway · Google I/O 2019