Doom (1993) Playable in a GitHub Readme
Details
- External ID
- 46511671
- Source
- HN
- Company
- —
- Product
- Doom (1993) Playable in a GitHub Readme
- Website domain
- github.com
- Launched
- Jan. 6, 2026
- Cohort
- —
- Upvotes
- 5
- Upvotes percentile
- 0.09617918313570488
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:25 p.m.
- Updated at
- Sept. 7, 2026, 9:25 p.m.
Description
I just had this really fun idea of making a playable version of DOOM on my GitHub profile after building "Doom" in a QR code last year (https://news.ycombinator.com/item?id=43729683) and I finally stopped procrastinating to try and build it.DoomMe is DOOM E1M1 map that can run on GitHub's markdown viewer which doesn't support javascript, web assembly or even iframes it works with a stateless engine with a capture of every possible position in the map (with 64 unit distance) captured in 4 directions and stitched together using graph logic with 8000+ WebP images and markdown filesBecause of it being stateless, I had to manually edit the WAD file to "open" the gates of E1M1 to use omgifol later to capture all valid positions inside the map!Open Source with MIT License and current version is <190 mb in size with all assets- Play it on my profile: https://github.com/Kuberwastaken- Blog post covering most of the process, implementation and failed tries: https://kuber.studio/blog/Projects/How-I-Made-DOOM-Run-Insid...
Enrichment
- Theme
- interactive simulations and creative experiments
- Vertical
- Media & entertainment
- Function
- —
- Audience
- B2C
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- doom playable in github readme
- Manually corrected
- False
Could you build this?
Partial Running interactive DOOM inside a GitHub README requires a complex headless backend that renders frames, exposes them via dynamic SVG/GIF images, and processes clicks via README hyperlinks or GitHub Actions state updates.
What it would actually take: Requires running a modified WebAssembly or native Doom engine inside an external serverless or containerized backend. User clicks on GitHub markdown links trigger HTTP GET webhooks to the server, which injects inputs into the running Doom instance, captures the framebuffer, renders it into dynamic SVG or animated GIF tiles, and invalidates/serves the cached image to GitHub's Camo image proxy.
Discussion
No comments on this launch.
Competitors
Other products that read as similar to this one — 67 launches clear the similarity bar, closest 8 shown.
Attention rank: #65 of 68 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 53 days after the earliest competitor.
- DoomPunks · ph · 2026-09-27 · 2 upvotes · similarity 0.50
- KiDoom · hn · 2025-11-25 · 362 upvotes · similarity 0.49
- doom_epub · github · 2026-09-12 · 15 upvotes · similarity 0.49
- DOOM in the kernel, or fibers in eBPF · hn · 2026-09-09 · 53 upvotes · similarity 0.47
- I wrote a DOOM clone in my own programming language · hn · 2026-04-28 · 34 upvotes · similarity 0.47
- We attached vGPUs to sandboxed Chromium then played Doom 3 x WASM on it · hn · 2026-03-19 · 9 upvotes · similarity 0.44
- TTF-DOOM · hn · 2026-04-06 · 68 upvotes · similarity 0.43
- I built a RISC-V emulator that runs DOOM · hn · 2026-05-03 · 50 upvotes · similarity 0.43