TypeScript types run DOOM in a stunt that pushes the language to extremes

# TypeScript types run DOOM in a stunt that pushes the language to extremes

Event date: 2025-02-26

A new video claims that the DOOM engine can run purely in TypeScript types, turning a notoriously practical language feature into the basis for a technical stunt. The supplied YouTube description is short, but it is enough to support a focused report about the demo and the question it raises: how far can type-level programming be pushed before it stops being useful and becomes performance art?

The evidence says the creators got the DOOM engine running "purely in TypeScript types" and that they did so "for real." That phrasing matters because it presents the result as a working demonstration rather than a mockup or an edited clip. The rest of the description suggests the project is part technical explanation, part curiosity-driven spectacle, with more videos planned about why the team did it.

A report should not overclaim on the engineering details because the excerpt does not explain the implementation, the runtime environment or what parts of the game were actually functional. But the core fact is still unusual enough to stand on its own: a famous game engine has apparently been encoded and executed at the type level, which is far outside normal TypeScript usage.

That kind of demonstration usually attracts two audiences. One is language enthusiasts who enjoy seeing where compile-time tricks break down or reveal hidden expressiveness. The other is developers who view the stunt as a reminder that tools can be bent in ways their designers never intended. In both cases, the point is less that anyone should ship production systems this way and more that the language's boundaries are broader than expected.

The video's existence also speaks to a long-running internet tradition: turning software constraints into a puzzle. DOOM has become a favorite target for these experiments because of its cultural status and the challenge of making it run in unusual environments. The novelty here is that the medium is TypeScript types, not an alternate device, browser, or embedded system.

The article should keep a clear line between the verified claim and any broader interpretation. The verified claim is the stunt itself. The interpretation is that it shows how type systems can be used in surprising, sometimes absurd ways. That distinction keeps the piece accurate while still giving readers a reason to care about it.

For many developers, the practical lesson is simple: language features can be pushed much further than everyday code would suggest. For everyone else, the result is just funny, impressive, and slightly alarming. TypeScript types are supposed to describe code, not host a game engine. But for one video, apparently, they did exactly that.